puntersedge

Bookmaker feed health

feed_health

Read-onlyIdempotent

Live health of every bookmaker feed: seconds since its last good poll, whether it is stale or degraded. For operations teams deciding whether to trust a price right now. Costs 1 credit. Every plan.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`summary`	Yes
`connectors`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld; the description adds the things they cannot: cost of 1 credit per call and availability on every plan. That cost detail genuinely affects invocation decisions. What it doesn't say is whether results are cached or how fresh 'live' actually is.

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

Conciseness5/5

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

Three short sentences, front-loaded with the payload, then the audience/use case, then cost and eligibility. Each sentence carries distinct decision-relevant information with zero filler.

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?

A zero-parameter, read-only diagnostic with an output schema covering the return shape. The description supplies use case plus billing/plan constraints — everything an agent needs before calling.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline for a no-arg tool. The description correctly implies no scoping inputs are needed since it reports on every feed.

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 verb and resource ('Live health of every bookmaker feed') plus the exact metrics returned (seconds since last good poll, stale/degraded flags). No sibling tool in the list does health monitoring, so the distinction is immediate.

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?

Explicitly frames the decision context — 'For operations teams deciding whether to trust a price right now' — which tells the agent when this tool is the right diagnostic step. It stops short of naming an alternative or stating when not to call it (e.g., vs. price_history for staleness investigation).

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

All puntersedge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.