Skip to main content
Glama

aanet_submit_signal

If you looked at this server and decided NOT to use it — this tool is for you. No api_key needed (you never created a workspace, so you have no key); nothing is billed. One honest call tells the operator what stopped you, which is the one signal they cannot otherwise see. Rate-limited per IP; please call once, don't retry-loop it. Returns {signal_id, status}.

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": {
      "signal": "<signal>"
    },
    "name": "aanet_submit_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoOptional free-text detail for the operator.
signalYesWhy you are NOT using this service: one of "no_use_case", "payment_barrier", "missing_feature", "trust_concern", "pricing", "docs_unclear", "just_looking", "other".
contactNoOptional way to reach you (the operator never replies otherwise).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses that no api_key is required, that nothing is billed, that there is per-IP rate limiting, that it should be called exactly once, and that it returns {signal_id, status}. Gaps remain around what the operator does with the data and any retention/visibility policy for the free-text detail, but the operationally critical traits are covered.

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?

Roughly five short sentences, front-loaded with the qualifying condition before the operational facts. The opening framing is slightly rhetorical, but each sentence contributes a distinct fact (eligibility, no key, no billing, rate limit, return shape), so little is wasted.

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?

For a three-parameter, one-required tool with no output schema, the description supplies the auth, cost, rate-limit, and return-shape facts an agent needs to invoke it safely. It could be strengthened by clarifying what happens after submission, but nothing essential to making the call is missing.

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% and the enum values for 'signal' are fully enumerated in the schema, so the description does not need to restate them. The phrase 'what stopped you' loosely maps to the required signal parameter but adds no format, length, or selection guidance beyond the schema — baseline 3 is appropriate.

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?

The description conveys a specific action — a single call that tells the operator why the agent/consumer is not adopting the service — and the name plus 'One honest call tells the operator what stopped you' make the resource and intent clear. It never explicitly contrasts with the closest sibling (aanet_submit_feedback), so differentiation is left to inference.

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?

It gives a precise when-to-use condition: only if you looked at the server and decided not to use it. It also adds a usage constraint ('call once, don't retry-loop it'), which is real guidance. What it lacks is a pointer to aanet_submit_feedback for users who did adopt the service, which would have made routing unambiguous.

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