Split override templates into a light index and a per-template detail tool - #4
Draft
92Infinitus92 wants to merge 1 commit into
Draft
Split override templates into a light index and a per-template detail tool#492Infinitus92 wants to merge 1 commit into
92Infinitus92 wants to merge 1 commit into
Conversation
Collaborator
Author
92Infinitus92
force-pushed
the
feat/mcp-template-index
branch
from
August 11, 2026 10:11
7d7e45d to
9ecf2de
Compare
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
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.
get_override_templatesreturned every template in full: properties, PDA layout, the whole constant catalog, and a ~160KB IDL inlined per template. An agent had to load all of that just to see what was available.This splits it in two:
get_override_templatesnow returns a light index - id, name, description, protocol, account type, tags, and ahasLlmContextflag. No properties, no IDL, no inlined options.get_override_template(templateId)returns one template's full detail, with each constant summarized as{label, description, optionsCount}instead of the raw option list.The flow is index → pick → detail →
search_constant_optionsfor a concrete value →create_scenario, and the guidance text walks the model through that order.Stacked on #3 (base
feat/pump-protocol); I'll retarget todeveloponce that merges.Greptile Summary
The PR replaces the heavyweight override-template listing with a lightweight index and adds a per-template detail tool.
hasLlmContextflag.get_override_templatefor properties, account-address data, summarized constants, and LLM context.Confidence Score: 5/5
The PR appears safe to merge with no concrete blocking or independently actionable non-blocking defects identified.
The new detail method is automatically registered by the existing MCP tool router, its parameter naming follows established conventions, and the updated index and detail responses preserve the data required by the documented scenario workflow.
Important Files Changed
Sequence Diagram
sequenceDiagram participant Client participant MCP as Surfpool MCP Client->>MCP: get_override_templates() MCP-->>Client: Lightweight template index Client->>MCP: get_override_template(templateId) MCP-->>Client: Properties, address, context, constant summaries opt Resolve constant value Client->>MCP: search_constant_options(templateId, query) MCP-->>Client: Matching concrete values end Client->>MCP: create_scenario(scenario) MCP-->>Client: Scenario resultReviews (1): Last reviewed commit: "Split override templates into a light in..." | Re-trigger Greptile