Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Get survey

get_survey
Read-only

Fetches a survey by UUID so you can retrieve its details for review or processing.

Instructions

Fetch a survey by uuid.

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": "get_survey"
  }
}

Input Schema

NameRequiredDescriptionDefault
survey_uuidYesSurvey UUID
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on what happens when the uuid is unknown, no indication of the organization parameter's per-call scoping behavior, and no hint at response shape.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity edges toward under-specification rather than optimal density.

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 simple read-only lookup with full schema coverage and annotations, the essentials are present. However, nothing tells the agent how missing/not-found cases behave or whether organization scoping affects the result, which matters for a multi-tenant 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 coverage is 100%, and the organization parameter is thoroughly documented in the schema itself (per-call only, non-persistent, header fallback). The description only repeats 'by uuid', which the schema already labels 'Survey UUID', 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 states a specific verb and resource ('Fetch a survey') and names the lookup key ('by uuid'), which distinguishes it from list_surveys and the aggregate tools like get_survey_statistics. It stops short of explicitly contrasting itself with any sibling, so it is clear but not maximally differentiating.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as list_surveys or get_survey_statistics, and no prerequisites or error conditions are mentioned. The agent must infer usage entirely from the name and the required uuid parameter.

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