Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

List respondents

list_respondents
Read-only

Retrieve survey respondent progress rows for status, timing, quota, and furthest question; PII is redacted unless include_pii and PII scope are authorized.

Instructions

List respondent progress rows for a survey (status, timing, quota, furthest question). PII redacted unless include_pii=true and token has mcp:pii scope.

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": {
      "survey_uuid": "<survey_uuid>"
    },
    "name": "list_respondents"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_piiNo
survey_uuidYes
organizationNoOrganization domain/slug for this call only. It does not persist. HTTP clients can also send X-DeepTrue-Org. Stdio defaults to DEEPTRUE_ORG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: respondent PII is redacted by default and only revealed under a combined flag-plus-scope condition, which tells the agent to expect masked data and what is required to unmask it. It omits pagination or row-limit behavior, keeping it below 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?

Two sentences, no filler, with the core operation front-loaded before the PII caveat. The parenthetical field list is dense but informative rather than redundant.

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?

For a read-only list tool with no output schema and a simple three-parameter input, the definition covers purpose, default redaction, and the PII unlock condition. However, it says nothing about result volume, pagination, or truncation, and the token-scope requirement is only noted in passing, which leaves gaps for an agent planning a call against a large survey.

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 only 33%, with no descriptions for include_pii or survey_uuid, so the description must compensate. It does so for the most consequential parameter by explaining that include_pii is gated on the mcp:pii token scope, and survey_uuid is self-evident from the phrasing; the organization parameter is already documented in the schema. The grant condition is the key semantic an agent needs and it is stated.

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 uses a specific verb and resource ('List respondent progress rows for a survey') and even names the returned fields (status, timing, quota, furthest question), so an agent knows exactly what it retrieves. It does not explicitly contrast itself with siblings like list_surveys or get_survey_statistics, 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 Guidelines3/5

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

Usage is implied by the framing: call this when you need per-respondent progress detail for one survey. The PII gate ('unless include_pii=true and token has mcp:pii scope') is a useful conditional, but there is no explicit statement of when to prefer this over get_survey_statistics or other survey-level tools.

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