Skip to main content
Glama

Best of Go

Repos of an owner

owner_repos
Read-onlyIdempotent

Every tracked Go repo of one GitHub user or organization, most stars first, with their totals.

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": {
      "owner": "<owner>"
    },
    "name": "owner_repos"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYesA GitHub user or organization, such as spf13.

Output Schema

NameRequiredDescriptionDefault
urlYes
typeYes
ownerYes
reposYes
repo_countYes
total_starsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds ordering ('most stars first') and that totals are included, but it does not explain what 'tracked' means, whether results are paginated or capped, or how many repos come back — meaningful gaps for a list operation.

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 tight sentence that front-loads the scope and ordering with no filler. Only 'with their totals' and the unexplained 'tracked' slightly blur the sentence, but nothing is wasted.

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?

An output schema exists, so return values need not be explained. However, for a list tool the definition omits result-size behavior and never clarifies the 'tracked Go repo' restriction, which is the single most consequential fact about what the agent will get back.

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% and there is a single required parameter, so the schema already documents 'owner' adequately. The description's 'one GitHub user or organization' adds nothing beyond the schema's own example, so the baseline of 3 applies.

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?

The description identifies a specific resource (repos belonging to one GitHub user or organization) plus ordering (most stars first) and payload (totals), which separates it from siblings like search_repos or topic_repos that operate on queries or topics rather than an owner. The qualifier 'tracked Go repo' is left undefined and introduces ambiguity about whether non-Go or untracked repos are excluded, keeping this short of a 5.

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 explicit when-to-use statement, no when-not-to-use, and no named alternative such as search_repos or get_repo. The only contextual signal is the phrase 'of one GitHub user or organization,' which merely restates the owner parameter rather than guiding tool selection.

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