Skip to main content
Glama

FoxAPIs data sources

GitHub release history

release_history
Read-onlyIdempotent

A repository's releases, cadence and streaks, read live and kept 6 hours: releases in the last 90 days, typical gap, longest gap and a plain sentence. 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": {
      "repo": "<repo>"
    },
    "name": "release_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesFor example: "vercel/next.js"

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 read-only, idempotent, open-world, and non-destructive, so the safety profile is free. The description adds genuinely new behavioral facts: results are fetched live but cached for 6 hours, each call costs 1 credit, empty answers are not charged, and a FoxAPIs key is required. These are exactly the operational constraints an agent should know before spending a call.

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?

Effectively two sentences, front-loaded with the returned metrics before pricing and auth details. Dense but every clause carries information; only the parenthetical '(free to start)' is mildly promotional rather than operational.

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?

With no output schema, the description must describe what comes back, and it does name the four return elements including the natural-language summary sentence. Combined with caching, per-call cost, billing exception, and credential requirement, an agent has everything needed to call this correctly and judge whether it is worth the credit.

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?

There is a single parameter with 100% schema description coverage, including an example value ('vercel/next.js'), so the schema carries the burden. The description adds no further format or validation detail for 'repo', which is acceptable at this schema richness — baseline 4 for a one-parameter tool.

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 repository's releases) and enumerates the concrete outputs: releases in the last 90 days, typical gap, longest gap, and a plain-language sentence. That is far more specific than a tautology. It does not, however, differentiate itself from siblings such as github_repo, so an agent cannot tell purely from this text whether it needs this tool or a general repo lookup.

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 metric-focused framing signals 'use this when you want release cadence/pacing rather than repo metadata.' There is no explicit when-to-use or when-not-to-use statement, and no named alternative. The cost note ('1 credit a call') hints at a usage tradeoff but is not guidance about selection.

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