Skip to main content
Glama

Data feed status

feed_health
Read-onlyIdempotent

Reports whether odds are currently arriving: the overall status, the number of in-play matches held, the age of the most recent live update and whether prematch data is on. Use it when prices seem frozen or a board is unexpectedly empty. Empty does not automatically mean broken: if fresh data stops arriving for too long, boards are intentionally held back instead of showing out-of-date prices, and REST replies flag this through the X-Data-Status (fresh/stale/unknown) and X-Data-Age-Ms headers. This tool tells the two situations apart.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses non-obvious system behavior: boards are intentionally held back when data goes stale instead of serving out-of-date prices, and REST replies expose X-Data-Status (fresh/stale/unknown) and X-Data-Age-Ms. That is exactly the kind of operational context annotations cannot convey.

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?

It is front-loaded with the answer the caller wants (what is reported), then the trigger, then the caveat. The closing sentence "This tool tells the two situations apart" largely restates the preceding explanation and is the one piece of slack in an otherwise tight description.

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 parameters and no output schema, the description carries the burden of describing return content, which it does by listing the four reported values. Combined with the annotations and the stale-data caveat, an agent has everything needed to call and interpret this 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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly adds no parameter detail rather than padding.

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?

The description names a specific verb and resource ("Reports whether odds are currently arriving") and enumerates exactly what the report contains: overall status, in-play match count held, age of the most recent live update, and prematch on/off. That scope makes it unambiguously a diagnostics tool rather than a data-retrieval tool like the board or price siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives an explicit trigger ("Use it when prices seem frozen or a board is unexpectedly empty") and an explicit caution against over-reading the result ("Empty does not automatically mean broken"), then frames the tool's role as disambiguating the two situations. No alternative tool needs to be named for the guidance to be actionable.

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