Skip to main content
Glama

quick

Read-onlyIdempotent

Find the module best matching a keyword and analyze it in one step, locating the relevant file or entity in a code graph so you can jump straight to the code.

Instructions

Find the module that best matches a keyword and analyze it in one step.

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": {
      "keyword": "<keyword>"
    },
    "name": "quick"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoList everything instead of stopping at 200 items.
keywordYesA word from a module path, file name or entity name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the search is best-match (not exhaustive) and that analysis happens in the same call, which is useful beyond the annotations. It does not say what 'analyze' returns or how best-match ties are resolved, so it stays at a moderate level.

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

Conciseness4/5

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

A single front-loaded sentence with no wasted words. It is efficient, though the brevity contributes to the missing guidance rather than being purely a virtue.

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

Completeness3/5

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

With no output schema, the description should clarify what the combined 'analyze' step yields, and it does not. The noun mismatch between the title ('feature') and the description ('module') also leaves scope unsettled. Annotations cover safety adequately, so the gap is moderate rather than severe.

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

Parameters3/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, including the 'all' flag's 200-item cap. The description only reinforces that 'keyword' is matched against module paths/names by saying 'best matches a keyword', adding nothing about syntax or matching rules. Baseline 3 applies when the schema carries the semantics.

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

Purpose3/5

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

The description gives a verb+resource ('find the module that best matches a keyword') plus a second action ('analyze it in one step'), which is more than a tautology. But 'quick' is an uninformative name and the annotation title says 'Find a feature' while the body says 'module', leaving what is actually searched and what 'analyze' produces ambiguous. It also does not distinguish this from siblings like find_function, entity, or query.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the many find_*/query/entity siblings, and no when-not guidance. The phrase 'in one step' hints that this is a shortcut combining search and analysis, but the agent must infer that selection rule rather than read it.

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