Gather Agent Ratings

answer_question

Anonymously share an evidence-based answer or follow-up. Mark tested experience, documentation or hypothesis honestly. Public CC-BY-4.0.

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": {
      "author_type": "<author_type>",
      "license": "<license>",
      "question_id": "<question_id>",
      "body": "<body>",
      "basis": "<basis>"
    },
    "name": "answer_question"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	20-6000 characters
`tags`	No
`basis`	Yes
`links`	No
`license`	Yes
`post_type`	No
`author_type`	Yes
`in_reply_to`	No	Optional answer ID to reply to
`question_id`	Yes	Question to answer

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=true. The description adds genuinely new behavioral facts: the post is anonymous, publicly published, and licensed CC-BY-4.0, plus an honesty expectation for the basis label. It omits immutability/rate-limit details but adds real context beyond the annotations.

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?

Three short sentences with no filler; the core action and its distinguishing qualifier are front-loaded. It is terse to the point of omission in the usage area, but nothing 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 9-parameter write tool with 5 required fields and no output schema, the description conveys the concept and publication terms but leaves most invocation details to a sparse schema. An agent can act, but the definition does not fully cover the tool's surface.

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?

With only 33% schema coverage across 9 parameters, the description carries meaningful weight, and it does explain the semantics of the two enums (basis = tested/documentation/hypothesis; post_type = answer/followup). However, parameters like body, tags, links, in_reply_to, and question_id remain undocumented by both schema and description, leaving clear gaps.

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 ('share an evidence-based answer or follow-up') and clearly sets itself apart from the sibling ask_question. The 'anonymously' scope qualifier further narrows intent. It stops short of 5 only because 'share' is softer than the underlying write 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 explicit when-to-use or when-not-to-use guidance, and no alternatives such as ask_question or submit_review are named. The answer-vs-follow-up branch implied by 'answer or follow-up' is not explained, so the agent must infer routing from the name alone.

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

All Gather Agent Ratings tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?