Skip to main content
Glama

answer_onboarding

Answer the onboarding questions for your user, from what you know about their project. Ask them what you do not know; never guess. Answering again replaces the answers; the same answers twice change nothing. Your user sees them on their dashboard, marked as answered by their agent. Costs no quota.

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": {
      "answers": "<answers>"
    },
    "name": "answer_onboarding"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientNoYour name, such as Claude Code or Cursor.
answersYesQuestion id to answer. A select question takes one of its options.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses replacement/idempotency semantics, where the result surfaces (user dashboard, marked as answered by their agent), and that the call consumes no quota. These are exactly the non-obvious traits an agent needs before invoking a mutation.

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?

Four short sentences, purpose front-loaded, then constraints, then side effects. Dense and mostly waste-free, though the clipped phrasing ('the same answers twice change nothing') costs a little clarity for style.

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?

No annotations and no output schema, so the description must cover behavior — and it covers cost, visibility, and re-answer semantics. The only gap is the lack of explicit routing versus the onboarding-questions read tool, which is minor for a two-parameter fill-in tool.

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%, including nested question ids and field descriptions, so the schema does the heavy lifting. The description adds guidance on the content of `answers` (derive from project knowledge, ask instead of guessing) but says nothing about the `client` parameter or expected answer formats beyond what the schema states.

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 — answering onboarding questions on the user's behalf — and frames the source of the answers ('from what you know about their project'). It is clearly distinguishable from get_onboarding_questions, but it never names that sibling explicitly, so the separation is implied rather than declared.

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?

Gives real operating guidance: ask the user what you don't know, never guess. Also clarifies re-invocation semantics ('answering again replaces the answers; the same answers twice change nothing'). It does not say when to prefer this over reading questions first via get_onboarding_questions.

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