Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

github_repository

Retrieves public metadata for a single GitHub repository from its URL, so you can verify and inspect repo details without manual lookups or API setup.

Instructions

github: Repository. GET /v1/github/repository. Get public metadata for one GitHub repository. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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_repository"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesGitHub repository URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose a meaningful cost model: 1 credit on success, free for errors, blocked/timed-out, invalid requests and cache hits. However, it says nothing about authentication needs, rate limits, or what "metadata" actually contains, leaving key behavioral questions unanswered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the leading fragments "github: Repository. GET /v1/github/repository." merely restate the name and internal route, adding no agent-relevant information. The cost sentences are informative but wordy, especially the not-found clause.

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 one-parameter read tool with an output schema absent, the definition covers purpose and billing but never characterizes the returned metadata. An agent knows how to call it and what it costs, yet not what it gets back, which is the main remaining gap.

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 the single url parameter includes an example (https://github.com/torvalds/linux). The description only restates that the target is one repository, adding no format, normalization, or acceptance rules beyond the schema.

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 gives a specific verb and resource: "Get public metadata for one GitHub repository." The phrase "one GitHub repository" implicitly separates it from list-style siblings like github_trending_repositories and github_user_repositories. It does not explicitly name any alternative, so it falls 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 this is for a single known repo URL rather than browsing or trending. There is no explicit when-to-use or when-not-to-use guidance and no stated alternative for related lookups (e.g. user or trending tools).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools