GitHub Platform Changelog — buy per-query in-session (githubchangelog)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: githubchangelog: GitHub Platform Changelog — Copilot, Actions & Security Changes. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What GitHub platform changes shipped this week?; Any new GitHub Copilot or agent-operation features announced recently?. FREE preview — no key, no payment. Try one of the sample questions now.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_preview"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	No	Public listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
`question`	No	Optional free-text question you'd ask this data (echoed back).

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 10, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that — no API key required, a 20-queries-per-session cap, and a per-query price — but the pricing statement ('0.01 USDC/query') sits awkwardly beside 'FREE preview — no key, no payment', creating ambiguity about what is actually charged.

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

Conciseness2/5

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

The text is cluttered with an emoji, a price line, two sample questions, and a redundant restatement of 'FREE preview — no key, no payment' that repeats the opening 'No API key needed'. The core fact — a free preview of a listing — is not front-loaded and is diluted by promotional filler.

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?

With no output schema, the description should clarify what a caller receives, but it only obliquely implies 'public metadata' via the schema's own description. Annotations cover the safety profile and the two optional params are documented, so the definition is workable, but the return shape and the preview-vs-paid boundary remain underspecified.

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 description coverage is 100%, with both 'slug' and 'question' fully documented in the schema, so the baseline is 3. The description adds nothing about parameter behavior — it does not explain the slug defaulting or that the question is merely echoed back — so it neither compensates nor detracts.

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

Purpose3/5

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

The description identifies the resource (the 'githubchangelog' GitHub Platform Changelog listing) and frames the tool as a 'FREE preview', but the actual action is buried under marketing copy and pricing text. It never states plainly that this returns a free sample of a listing's public metadata, so the verb+resource pairing is only inferable.

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?

'Try one of the sample questions now' and 'FREE preview — no key, no payment' imply this is a try-before-you-pay entry point, which hints at when to use it. However, it never names the paid alternative (data_session_query) or states when to graduate from preview to a real session, leaving the routing decision to inference.

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

All GitHub Platform Changelog — buy per-query in-session (githubchangelog) tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?