Skip to main content
Glama

Synapse

Find existing code to reuse

find_existing
Read-onlyIdempotent

Search existing functions, classes and methods by what they do (e.g. "format currency"). Use before writing a new helper.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "repository": "<repository>"
    },
    "name": "find_existing"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat the code should do.
repositoryYesPublic GitHub repository as "owner/name" (e.g. "pallets/flask") or its github.com URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is fully covered. The description adds little beyond that: it does not say whether matching is semantic or substring, how results are ranked or capped, or what happens when nothing matches. Useful context, but not rich behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the what and the when front-loaded in that order. No filler, no restatement of the title beyond what adds information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only search with strong annotations and no output schema, the definition covers purpose, query semantics and timing. A brief note on result ranking or limits would close the remaining gap, but nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented; the description nevertheless adds real meaning by clarifying that the query is a natural-language behavior description rather than a symbol name, reinforced by the 'format currency' example. That distinction materially changes how an agent should phrase the query.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and resource group (existing functions, classes and methods) plus the retrieval mode ('by what they do'), which separates it from a plain code reader like read_code. It does not name a sibling explicitly, so differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use before writing a new helper' gives a concrete trigger condition for invoking the tool. It stops short of exclusions or naming alternatives (e.g. repo_map for structure, read_code for a known path), so the agent must infer when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources