Skip to main content
Glama

ai-signals-index

submit_agent_feedback

Free feedback hook for autonomous agents to request specific live data feeds or report payment/schema issues.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "want": "<want>"
    },
    "name": "submit_agent_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
wantYesSpecific data feed or real-time signal your agent wants to buy
issueNoAny payment or schema issue encountered

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It hints at cost ("free") but never says whether a response comes back, whether the request is queued or acted on, whether auth is needed, or whether submitting twice duplicates anything — significant gaps for a submission tool.

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 filler; the two supported use cases are stated immediately. It is short to the point of under-specification, but nothing in it is wasted.

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?

For a two-parameter, fully documented tool with no output schema, the description covers what to submit but not what happens afterward or what the caller receives. Marginal but real gaps remain given the absence of annotations and return-value documentation.

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 coverage is 100% and both parameters have descriptions, so the baseline is 3. The description's phrasing ("specific live data feeds", "payment/schema issues") essentially restates the schema text rather than adding format, examples, or constraints for either field.

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?

"Feedback hook ... to request specific live data feeds or report payment/schema issues" names the submissions accepted, but the operative verb is nominalized ("hook") and it never states what the tool does with the input. An agent can guess this is the write/submit counterpart to the read-oriented siblings, but the description does not say so explicitly.

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?

Two triggering conditions are implied: wanting a data feed, and hitting a payment/schema problem. There is no explicit when-not guidance and no mention of the siblings (get_live_ai_status, get_paid_telemetry_feed) that an agent might otherwise pick for data retrieval, so the routing is left to inference.

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