Skip to main content
Glama

read_question

Read-onlyIdempotent

Read one question by id, list questions in a block, or audit survey-level question data (skip rules, hidden questions, randomization) via survey_id + include.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoSurvey- or question-level read-backs beyond the core question payload
block_idNoList all questions in this block when question_id is omitted
survey_idNoSurvey UUID for survey-level audits (use with include)
question_idNoQuestion UUID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that include pulls read-backs beyond the core question payload. It says nothing about permission scoping on hidden/trashed content or result size, which would be genuinely additive context.

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?

A single sentence that is front-loaded with the primary use case and then packs the two secondary modes compactly. No filler. The 'survey_id + include' shorthand is slightly terse but readable.

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?

An output schema exists, so return-value description is unnecessary, and annotations cover safety semantics. The description addresses all four parameters and all three operating modes. What remains missing is edge-case behavior, such as combining question_id with survey_id, which is minor for a read 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%, with per-property descriptions for include, block_id, survey_id, and question_id. The description's mode framing ('via survey_id + include', 'list questions in a block') largely restates what the schema already documents. With the schema carrying the parameter burden, baseline 3 is correct.

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 gives a specific verb plus resource and enumerates three distinct call modes: single question by id, listing questions within a block, and survey-level audits of skip rules, hidden questions, and randomization. That is enough for an agent to separate this from edit_question/delete_question and from read_block. It stops short of naming a sibling outright, which keeps it from a 5.

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?

Usage is conveyed by mapping inputs to modes: question_id for a single read, block_id for a block listing, and survey_id together with include for audit read-backs. The agent can pick the right call shape without inference. It does not state precedence when question_id and survey_id are both supplied, nor any when-not-to-use case.

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