Skip to main content
Glama

Best of Go

Search Go repos

search_repos
Read-onlyIdempotent

Search Go repositories by words, best match first. Popular repos rank higher among equal matches.

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_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many repos to return, 1 to 50. Default 10.
queryYesWords to search for, such as orm or http router. Every word must match the repo name, owner, topics, or description.

Output Schema

NameRequiredDescriptionDefault
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses the ranking model — best match first, with popularity as a tiebreaker among equal matches — which an agent cannot get from structured fields. It does not discuss pagination or empty-result handling, and the output schema already covers return shape.

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 no waste; the core operation is front-loaded and the ranking caveat follows immediately. Nothing is repeated or padded.

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 full schema coverage, annotations, and an output schema, the description covers purpose and result ordering adequately. Only the routing context versus sibling search tools is missing.

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 the baseline is 3. The description restates the matching rule (every word must match name, owner, topics, or description) that the query parameter already documents, and adds nothing about limit or query syntax beyond the schema.

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?

"Search Go repositories by words" gives a specific verb and resource, and "best match first" states result ordering. It is clearly a keyword search rather than an owner/topic/trending listing, though it never names those sibling tools to make the contrast explicit.

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?

Usage is only implied: the word-based query requirement suggests the tool is for keyword lookup, and callers are left to infer when to prefer owner_repos, topic_repos, or trending_repos. No when-not-to-use condition or alternative is stated.

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