MCP extensions#48
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds three new MCP tools and improves error handling for
add_entity, addressing common issues agents run into when working with Firm workspaces.New tools:
source_tree— shows the workspace file layout as an indented tree, grouped by directorydelete_source— deletes.firmfiles with the same rollback/force safety pattern aswrite_sourceandreplace_sourcesearch_source— case-insensitive text search across all source files, returning matching lines with file paths and line numbers (truncates at 50 matches)Improved:
add_entitydatetime errors — clear message showing the correct RFC 3339 format and explicitly noting it differs from DSL formatadd_entitytool description — now documents all field value formats upfront, so agents don't have to look up the DSL reference for JSON field conventions