Skip to main content
Glama

AIDNode | AI Agent Support Network

submit_beta_feedback

Optional and free. Report whether AIDNode helped and whether your operator might consider the proposed $0.005/use price. A bot answer is NOT purchase authorization. Feedback is stored privately and is not a testimonial.

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": {
      "checkpoint": "<checkpoint>",
      "service": "<service>",
      "helpful": "<helpful>",
      "would_reuse": "<would_reuse>",
      "would_pay_half_cent": "<would_pay_half_cent>",
      "outcome": "<outcome>"
    },
    "name": "submit_beta_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNo
helpfulYes
outcomeYes
serviceYes
checkpointYes
would_reuseYes
would_pay_half_centYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose meaningful behavior: submissions are stored privately, are not testimonials, and a bot-completed answer is explicitly not a purchase authorization. These are exactly the consent/privacy/commitment facts an agent needs before writing. It still omits whether repeat submissions are allowed or what a call returns.

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?

Three short sentences, front-loaded with the optional/free framing, then purpose, then the two critical caveats. Nothing is padded and each sentence adds a distinct fact.

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

Completeness2/5

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

This is a 7-parameter submission tool with no annotations, no output schema, and undocumented parameters, including a non-obvious numeric checkpoint enum. The description covers the consent dimension well but leaves an agent unable to confidently map values onto checkpoint, service, or outcome — a substantive gap for a mutation-style tool with this schema surface.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 7 parameters, and the description only gestures at two of them (helpful, would_pay_half_cent). The most opaque field, checkpoint with enum [10,50,100,250,500], plus service, outcome, would_reuse and comment get no explanation at all; the enum values are terse enough that an agent cannot confidently infer semantics from the schema alone.

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 names the specific action (report) and the specific content being reported: whether AIDNode helped and whether the operator would consider the $0.005/use price. That is more than a restatement of the name and conveys the beta-feedback intent, though it never explicitly contrasts with the sibling tools (monitor, repair, verify, witness), which serve clearly different functions.

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?

"Optional and free" signals that calling this is discretionary rather than required by a workflow, which is real usage context. However, there is no statement of when in a session feedback should be submitted, whether it should be submitted once or repeatedly, or what to do if the user declines — the guidance is implied rather than explicit.

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.