FormFav Horse & Greyhound Racing

Check request quota

get_usage

Read-onlyIdempotent

Check how much of the daily request quota is left. Free to call: it does not count.

The quota is a rolling 24-hour window, not a midnight reset, shared by all of the
user's API keys and connected apps. Every other tool call counts as one request.

Returns tier, unlimited, limit, used and remaining, and overQuota. While overQuota is
true, other tools fail with a rate-limit error and availableAt (UTC) says when requests
are allowed again. used, remaining and overQuota can be missing if live counts are
briefly unavailable; limit and remaining are missing on an unlimited tier.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, it discloses that the quota is a rolling 24-hour window shared across all API keys and connected apps, that other tool calls consume quota, which fields are returned, and how overQuota affects other tools. It also documents exactly which fields may be missing and under what conditions.

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?

The description is front-loaded with the core purpose and cost, then provides structured details about quota behavior and return fields. Every sentence adds useful information without unnecessary repetition.

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?

For a zero-parameter read-only quota check with an output schema, the description is complete. It explains return values and edge cases such as missing fields, overQuota behavior, and the rolling window, leaving no important gaps.

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 has zero parameters, so there is no parameter semantics burden. The schema coverage is 100%, and no additional parameter guidance is needed.

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 states a specific action and resource: checking the remaining daily request quota. It is immediately distinguishable from all sibling tools, which retrieve racing data rather than quota information.

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?

The description clearly explains that this tool is free to call and does not count toward the quota, while every other tool call does. It also explains the consequence of overQuota being true, but does not explicitly recommend when to call it relative to other tools beyond the implied check-before-use scenario.

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

All FormFav Horse & Greyhound Racing 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.

Resources

Need Help?