Skip to main content
Glama

Report your person's setup answers

answer_setup
Read-only

Call after asking your person the setup_chat questions start_agent_run gave you, in a run they started. run: from start_agent_run. report: setup_chat.report, exactly (null when it was null). confirmed: true only when they said yes to your one-sentence account of what you do. said: their answer to that question, exactly. name: what they want you called. purpose: the sentence you showed them (or their correction). systems: any systems they added. documents: links they gave you. Rithmo records it as your report.

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": {
      "run": "<run>",
      "confirmed": "<confirmed>",
      "said": "<said>"
    },
    "name": "answer_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
runYes
nameNo
saidYes
reportNo
purposeNo
systemsNo
agent_keyNo
confirmedYes
documentsNo
instructionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Beyond the annotations, the description adds meaningful behavior: values must be carried over exactly ('setup_chat.report, exactly (null when it was null)', 'said: their answer ... exactly'), and 'Rithmo records it as your report' explains that the answer is persisted against the run, consistent with idempotentHint=false and destructiveHint=false. There is mild tension with readOnlyHint=true, since recording is a state effect, and nothing is said about what happens with an invalid or already-used `run`, so the disclosure is helpful but incomplete.

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?

The trigger sentence is front-loaded and the rest is a compact per-parameter glossary with no filler; size is appropriate for a ten-parameter tool. The telegraphic '`x`: ...' fragments are efficient but occasionally terse enough to require a second read.

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 high-parameter, no-output-schema, non-idempotent reporting tool, the definition covers the prerequisite call, the exactness requirements, and eight of ten fields. It is not fully complete because `agent_key` and `instructions` are undocumented and no failure or duplicate-submission behavior is described.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the full burden and mostly delivers: it gives origins and exactness rules for `run`, `report`, `confirmed` ('true only when they said yes to your one-sentence account'), `said`, `name`, `purpose`, `systems`, and `documents` — far more than the raw JSON schema conveys. Two of the ten parameters, `agent_key` and `instructions`, are never mentioned anywhere.

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 a specific verb and resource: report the person's `setup_chat` answers for a run started by `start_agent_run`. It is clearly distinguishable from `start_agent_run` itself, but it never contrasts with sibling report/declare tools such as `declare_my_setup` or `report_agent_run`, so the agent has to infer the boundary.

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?

The trigger is stated explicitly: call this only after asking the person the `setup_chat` questions that `start_agent_run` returned, within a run they started. That is a real precondition with a named upstream source. It stops short of exclusions, though — nothing says what to do if questions were never delivered or how this differs from the declare/report siblings.

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