Skip to main content
Glama

search_smw_code

Search for code within the GitHub repository: "ethanhunt1981/smw-reverse-engineering-kb" using the GitHub Search API (exact match). Returns matching files for you to query further if relevant.

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>"
    },
    "name": "search_smw_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number to retrieve (starting from 1). Each page contains 30 results.
queryYesThe search query to find relevant code files

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden and does disclose meaningful behavior: exact-match semantics via the GitHub Search API and the fact that results are files to be queried further. It omits rate limits, authentication requirements, and whether an empty result is possible, which matter for an API-backed search tool.

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, front-loaded with the target repository and the search mechanism, with no filler. Every clause contributes scope or workflow 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 search tool with full schema coverage and no output schema, the description supplies scope, matching behavior, and a follow-up path. It is nearly complete, with only auth and result-count behavior left unstated.

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 description coverage is 100%, so both 'query' and 'page' are already documented in the schema, making 3 the baseline. The description adds no query syntax guidance beyond 'exact match', so it does not meaningfully extend parameter meaning.

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 (code) and pins the scope to a named repository, which is far more than a tautology. It does not explicitly distinguish itself from the sibling search_smw_docs, so an agent must infer that 'code' means source files rather than documentation.

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

Usage Guidelines3/5

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

The clause 'Returns matching files for you to query further if relevant' implies a two-step workflow (search, then fetch), which is a useful hint. However, there is no explicit statement of when to prefer this over search_smw_docs or when not to use it, leaving the choice between the two search siblings to inference.

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