PreShiftIQ

Answer an assessment question in the card

answer_question_in_card

Records the option the person chose in the PreShiftIQ assessment card for the next question of the assessment in this conversation, exactly as answer_question does, and returns the next question, the updated handle and the next step. It is called by the card when the person clicks an option, and is not offered to the assistant. PreShiftIQ stores no answer from this tool; answers given here are kept only if the client continues to preshiftiq.com, signs in and agrees there.

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": {
      "handle": "<handle>",
      "question_id": "<question_id>",
      "value": "<value>"
    },
    "name": "answer_question_in_card"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes
`handle`	Yes
`question_id`	Yes

Output Schema

Name	Required	Description	Default
`handle`	Yes
`answered`	Yes
`next_step`	Yes
`start_url`	Yes
`next_question`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Adds real behavioral context beyond the annotations: it discloses the return payload (next question, updated handle, next step) and a data-persistence caveat that answers are not stored by this tool unless the client continues, signs in, and agrees. The caveat about non-persistence sits slightly in tension with readOnlyHint=false and is not fully reconciled, which keeps it from a 5.

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 compact sentences, front-loaded with the action and the return shape, then the invocation rule, then the storage caveat. The persistence sentence is long but earns its place as risk-relevant context.

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?

An output schema exists, so return values need not be spelled out, and the description covers invocation and persistence well. However, with three required, entirely undocumented parameters, an agent reading this alone cannot interpret handle, question_id, or multi-value answers.

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?

Schema description coverage is 0%, so the description carries the burden, yet it never explains handle, question_id, or value. It only implies value is the chosen option and that handle is updated on return; the fact that value may be an array of up to 60 strings is left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: records the chosen option in the PreShiftIQ assessment card for the next question, and returns the next question, updated handle, and next step. It explicitly distinguishes itself from the sibling answer_question by noting it is invoked by the card and is not offered to the assistant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger (the card calls it when the person clicks an option) and an explicit exclusion (not offered to the assistant), plus names the equivalent sibling path via answer_question. An agent knows both when this fires and when to route elsewhere.

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

All PreShiftIQ tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.