Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

GitHub repo data: stars, forks, release

github_repo
Read-only

GitHub repository data in one call: stars, forks, watchers, open issues and pull requests, main language and language shares, topics, license, default branch, created and last-push dates, archived and fork flags, and the latest release with its tag and date. Give owner/name or a github.com URL; public repositories only, no user profile data. Use to vet a dependency, check whether a project is alive, compare libraries or enrich a list of repos. Example: repo=vercel/next.js. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "github_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository as owner/name, e.g. vercel/next.js, or its github.com URL
ownerNoOwner, only when repo is given as a bare name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Beyond the readOnly/destructive/openWorld annotations, the description adds genuinely useful operational context: exact pricing ($0.002/call), first 25 free, failed calls free, x402 USDC or card key auth, and the warning that repeats are not free. That last point usefully explains the otherwise puzzling idempotentHint=false on a pure read. It is strong disclosure, but the bar is lower with annotations already covering safety, so this sits at the high end of adequate rather than exceptional.

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?

Front-loaded with the returned-field inventory, then usage, then input form, then pricing — a sensible order. It is one dense block rather than separated lines, and the field list is long, but nearly every clause carries decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description's enumerated field list effectively serves as the return-value contract, and it covers that thoroughly. Input format, access limits, cost, and side-effect profile are all present, leaving nothing an agent needs before calling it.

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 coverage is 100% and both parameters are already documented there, including the owner/name and github.com URL forms. The description restates the accepted input format and repeats the vercel/next.js example without adding syntax, defaults, or edge-case behavior (e.g. case sensitivity, how URL fragments are handled). Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and enumerates exactly what it returns: stars, forks, watchers, open issues/PRs, languages, topics, license, default branch, dates, flags, latest release. Scope exclusions ('public repositories only, no user profile data') further sharpen it against adjacent tools like github_search or check-counterparty style lookups.

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

Usage Guidelines4/5

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

Gives concrete use cases: 'vet a dependency, check whether a project is alive, compare libraries or enrich a list of repos', plus an input example. It does not name an alternative tool or state when to prefer a sibling (e.g. github_releases for release history), so it stops short of full routing guidance.

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.