Skip to main content
Glama

ai-signals-index

get_paid_telemetry_feed

Full 24-hour human-AI friction telemetry, model sentiment scores, outage verification, and automated task routing matrix ($0.05 USDC via x402 v2 on Base).

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_paid_telemetry_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional archive date in YYYY-MM-DD format (defaults to latest feed.json)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does add one genuinely important trait: the tool is paid, at $0.05 USDC via x402 v2 on Base, which tells the agent a payment flow is prerequisite. Beyond that it is silent on other behavior — no indication of whether reads are safe/non-destructive, what happens when the archive date is missing or invalid, response shape, or rate limits.

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?

A single front-loaded sentence with no padding; every clause names a distinct data category and the pricing parenthetical is compact. It loses a point only because the dense comma list reads as keyword stuffing rather than structured information, making the key facts slower to extract.

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?

One optional parameter and no output schema means the description must explain what comes back, and it only partially does so by naming content categories rather than describing the response structure. The payment disclosure is valuable, but the mechanics of paying and the shape of the returned feed are left unstated for a tool with no output schema to fall back on.

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%: the single optional date parameter is fully documented in-schema with format (YYYY-MM-DD) and the default-to-latest-feed behavior. The description adds nothing about the parameter, but with coverage this high the schema is doing the work, so the baseline of 3 applies.

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 names a specific resource and enumerates its contents (friction telemetry, sentiment scores, outage verification, routing matrix), which is more informative than the name alone. However, it is a bare noun phrase with no verb, so the actual action (fetch/retrieve a feed) is only inferable from the tool name and the archive-date parameter. An agent gets the subject matter but not an explicit statement of the operation.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no reference to the siblings get_live_ai_status or submit_agent_feedback. A reader cannot tell from the text when to prefer this 24-hour feed over a live status check, nor whether the date parameter implies historical backfill versus defaulting to current data.

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