Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_sports_payment_telemetry

Retrieve aggregate 24h/7d failure telemetry for the sports-bet payment rail, covering shadow-settlement proofs, cache hits, honest failures, last failure reason, and daily shadow-cap usage.

Instructions

[FREE] Failure telemetry for the sports-bet payment rail.

Aggregate counts of shadow-settlement proofs, cache hits and honest failures over 24h and 7d, the last failure reason, and daily shadow-cap usage. Aggregates only - no caller identity is ever stored.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does a fair job: it discloses that output is aggregate-only, that no caller identity is stored, and the exact time windows (24h and 7d) and metrics returned. It does not explicitly label the operation read-only or mention caching/rate-limit behavior for the 'cache hits' figure, which keeps it below a 5.

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?

Front-loaded with the one-line purpose, followed by the metric inventory and a privacy note; every sentence adds information and nothing is repeated. The '[FREE]' marker is compact and meaningful for selection.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because there is no output schema, the description must describe return values and it does so concretely: counts over 24h and 7d, last failure reason, and daily shadow-cap usage. Only minor gaps remain (output shape/units and confirmation that the call is side-effect free).

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 there is no parameter semantics to explain; the description correctly spends no space on arguments and instead describes the returned metrics. Baseline 4 applies for a parameterless 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?

States a specific verb and resource — failure telemetry for the sports-bet payment rail — and enumerates what is counted (shadow-settlement proofs, cache hits, honest failures). It implicitly separates itself from sibling proof/status tools like get_sports_payment_proof and get_sportsbook_status, though it never names them.

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 implied rather than stated: an agent can infer this is the diagnostic view for the payment rail, and the '[FREE]' tag signals a cost-free alternative to paid siblings. However, there is no explicit when-to-use, when-not-to-use, or named alternative such as get_sports_payment_proof.

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

Deploy Server

Other Tools