Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Get survey statistics

get_survey_statistics
Read-only

Retrieve survey statistics for a specific project by its UUID. Use it to fetch aggregated survey metrics needed for reporting or analysis.

Instructions

Fetch survey statistics by project 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": {
      "project_uuid": "<project_uuid>"
    },
    "name": "get_survey_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationNoOrganization domain/slug for this call only. It does not persist. HTTP clients can also send X-DeepTrue-Org. Stdio defaults to DEEPTRUE_ORG.
project_uuidYesProject UUID used by statistics endpoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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 mention of what the statistics represent, whether results are computed live or cached, or whether they reflect partial fielding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted words, but it is terse to the point of under-specification rather than efficient. Front-loading is fine; the missing content is what costs it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description is the only place an agent could learn what 'statistics' are returned and in what shape — and it says nothing about that. For a read tool whose entire value is the returned data, this is a meaningful gap.

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%, including the organization override, so the schema carries the parameter burden. The description only restates the project_uuid requirement without adding format, source, or lookup guidance — baseline 3 applies.

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

Purpose3/5

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

States a clear verb (fetch) and resource (survey statistics) scoped by project uuid, so the basic action is legible. However, 'statistics' is undefined — no indication whether this means response counts, completes, incidence, or quota data — and nothing distinguishes it from the sibling get_survey, which plausibly also returns survey-level data.

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?

No when-to-use guidance at all: no condition selecting this over get_survey, get_feasibility, or get_report, and no stated prerequisites. The agent must infer usage purely from the name.

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