Skip to main content
Glama

Novig market data (novigapi.com)

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

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does well: it discloses idempotency ('the same answers twice change nothing'), replacement semantics, user-visible effect on the dashboard, and that the call costs no quota. It stops short of stating permissions or what errors occur for an invalid select option.

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?

Four short sentences, each carrying distinct information: the action, the don't-guess rule, the replace/idempotency semantics, and the visibility-plus-cost note. Nothing is repeated or padded.

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 small two-parameter write tool with no output schema, the description covers effect, idempotency, and side effects well. The main omission is any pointer to how to obtain valid question ids, which matters given the nested answers object.

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 coverage is 100%, so the nested question ids, required 'data_wanted'/'use_case', and the 'client' field are already documented. The description adds no extra meaning about parameter formatting or how the answers object maps to question ids, so baseline 3 applies.

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 opens with a specific verb and resource: 'Answer the onboarding questions for your user.' It clearly implies a write/answer action as distinct from the sibling get_onboarding_questions, which would only read questions, though it never names that sibling.

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?

It gives useful behavioral rules ('Ask them what you do not know; never guess'), but never says when to call this versus get_onboarding_questions or finish_signup, nor that question ids should come from get_onboarding_questions. Usage is implied rather than routed.

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.