Skip to main content
Glama

AutoTasker Hub — China Social Data API

gh_repo_info

GitHub public repo metadata: stars, forks, language, topics, license. No auth. $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault
repoYes
ownerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: 'No auth' (no credentials needed) and '$0.01 USDC' (per-call cost, which matters for an agent deciding whether to call it). It says nothing about error behavior for private or nonexistent repos, rate limits, or whether the cost is per-call or per-success, leaving meaningful behavioral gaps.

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?

The definition is short and front-loads the resource and returned fields before the operational facts (auth, cost). The telegraphic fragments ('No auth. $0.01 USDC.') are efficient rather than wasteful, though they read as notes more than prose.

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?

For a simple two-parameter lookup with no output schema, listing the returned fields, plus cost and auth status, covers the essentials. However, the missing parameter format guidance and error/not-found behavior leave it adequate rather than complete.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the schema provides no meaning for 'owner' and 'repo' beyond their names. The description does not clarify the expected format (e.g., bare owner name vs. 'owner/repo' combined, case sensitivity, URL acceptance), so an agent must guess, and neither structured field nor description compensates for the gap.

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 verb-less but unambiguous resource ('GitHub public repo metadata') and enumerates the returned fields (stars, forks, language, topics, license), so an agent knows exactly what it fetches. It does not explicitly contrast itself with any sibling, but none of the listed siblings (color_info, pypi_info, arxiv_search) overlap in domain, so confusion risk is low.

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 when-to-use guidance, no prerequisites, and no mention of alternatives or limits on which repos qualify beyond the word 'public'. The agent must infer from the name alone that this is the tool for looking up a specific repository's stats.

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.