Skip to main content
Glama

Best of Go

Get a Go repo

get_repo
Read-onlyIdempotent

One repo: total stars, rank among all tracked Go repos, stars gained in the last 7 days, 30 days, and 12 months, topics, archived state, and last push.

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": {
      "repo": "<repo>"
    },
    "name": "get_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesThe repo as owner/name, such as pressly/goose.

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
rankYes
ownerYes
starsYes
topicsYes
archivedYes
full_nameYes
pushed_atNo
categoriesYes
created_atNo
github_urlYes
owner_typeYes
descriptionYes
stars_gainedNo
tracked_reposYes
stars_gained_inYes
star_history_urlYes
classified_categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / classified_category
      Added value: +{
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / categories
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "null",
      +    "array"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "full_name",
      -  "owner",
      -  "name",
      -  "description",
      -  "topics",
      -  "stars",
      -  "url",
      -  "github_url",
      -  "owner_type",
      -  "archived",
      -  "rank",
      -  "tracked_repos",
      -  "stars_gained_in",
      -  "star_history_url"
      -]New value: +[
      +  "full_name",
      +  "owner",
      +  "name",
      +  "description",
      +  "topics",
      +  "stars",
      +  "url",
      +  "github_url",
      +  "owner_type",
      +  "archived",
      +  "categories",
      +  "rank",
      +  "tracked_repos",
      +  "stars_gained_in",
      +  "star_history_url"
      +]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the ranking scope ('among all tracked Go repos'), which is genuinely useful context, but it does not disclose error behavior for unknown repos, data freshness, or ranking staleness.

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 compact sentence that front-loads the core resource and then lists return fields with zero filler. It reads as a fragment rather than a full sentence, but nothing is wasted and it is easy to scan.

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?

With an output schema present, the description need not explain return values, and the annotations plus 100% schema coverage handle safety and the single parameter. What remains thin is routing guidance against the many sibling tools, which a complete definition would address.

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?

There is only one parameter and schema description coverage is 100%; the schema already explains the owner/name format with an example (pressly/goose). The description adds no additional meaning about the identifier beyond what the schema states, so the baseline 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 names a specific resource (a single repo) and enumerates exactly what it returns: total stars, rank among tracked Go repos, gains over 7d/30d/12mo, topics, archived state, last push. That is far more specific than a tautology, but it never contrasts itself with siblings like star_history or owner_repos, so an agent must infer the distinction from names alone.

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: 'One repo' suggests fetching metrics for an already-known owner/name identifier. There is no explicit when-to-use guidance, no mention of when to prefer star_history for time-series data or search_repos for discovery, and no stated prerequisites.

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