Skip to main content
Glama

Read the member's answers

get_answers
Read-onlyIdempotent

The member's saved answers, finished questions, the questions only they can answer, and questions about them. Actions: questions, library, finished, ask_library. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "get_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "library",
      -  "finished",
      -  "ask_library",
      -  "help"
      -]New value: +[
      +  "questions",
      +  "library",
      +  "finished",
      +  "ask_library",
      +  "help"
      +]
  2. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. What the description adds is the meta-affordance that action "help" enumerates each action's fields, which is genuinely useful behavior for a dispatcher tool. It discloses nothing about result shape, pagination, or scope limits per action.

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?

Two short sentences with no filler, and the action list plus the help hint are front-loaded. The first sentence is a comma-spliced noun phrase that reads ambiguously, but no words are wasted.

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?

For a four-way dispatcher whose params object is free-form (additionalProperties: true) and has no output schema, the agent needs at minimum a one-line summary of each action and its expected fields. Instead the definition offloads all of that to a prerequisite help call, forcing a two-step discovery round trip. The help affordance is a real mitigation but does not make the definition self-sufficient.

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?

The action enum is already fully enumerated in the schema, and the description largely repeats four of those five values without explaining what any of them do. The free-form nested params object is not clarified at all; the description defers entirely to a runtime "help" call rather than adding meaning. With only 50% schema coverage, this delegation leaves the agent unable to predict required fields before invoking.

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 is a noun-phrase list of the four data sets retrievable (saved answers, finished questions, private questions, questions about the member) plus four action names. It conveys the domain but never states a verb or the mapping between the listed data categories and the action names, so the agent must guess which action returns which set. It also gives no explicit differentiation from the sibling manage_answers tool.

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 and no exclusion against alternatives such as manage_answers or ask_otto. The only routing hint is the procedural note to call action "help", which explains how to discover fields rather than when this tool is the right choice.

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.