Skip to main content
Glama

FoxAPIs data sources

GitHub repository

github_repo
Read-onlyIdempotent

Stars, forks, open issues, language, licence, topics and dates for a public GitHub repository, from its link. Costs 1 credit a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": {
      "url": "<url>"
    },
    "name": "github_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFor example: "https://github.com/torvalds/linux"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false) and open-world access, yet the description still adds real value: a cost of 1 credit per call, a no-charge policy when no data is returned, and the requirement for a FoxAPIs key. Those are exactly the operational facts annotations cannot express; only per-call latency or rate limits are missing.

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?

Two tight sentences: the payload is front-loaded, then cost and prerequisites. Nothing is redundant, though the '(free to start)' parenthetical leans promotional rather than informative.

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 carries the return-value burden and does so by listing the fields returned. Combined with cost, key requirement, and the public-repo constraint, an agent has everything needed to decide and invoke correctly for this simple one-parameter tool.

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

Parameters4/5

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

With a single parameter and 100% schema coverage, the schema already documents the url field with a concrete example. The description reinforces the semantics by saying the input is the repository's link and by noting it must be public, which is a meaningful constraint the schema does not state.

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 concrete resource (a single public GitHub repository identified by its link) and enumerates the returned fields: stars, forks, open issues, language, licence, topics, dates. That separates it in spirit from github_search and github_user, though it never names those siblings explicitly, which keeps it just 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 Guidelines3/5

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

Usage is only implied: the agent can infer 'pass a repo URL, get repo stats' and that only public repositories are supported. There is no explicit statement of when to prefer this over github_search or github_user, and no exclusion or prerequisite guidance beyond the API-key note.

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