Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

List surveys

list_surveys
Read-only

List surveys in the active organization, with pagination and an optional organization override for a single call. Use it to browse available surveys before retrieving details or statistics.

Instructions

List surveys in the active organization.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
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
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description's one contribution is the data scope ('active organization'), which tells the agent results are org-bounded; it says nothing about pagination behavior, default page size, or result ordering, which matter for a list tool exposing limit/offset.

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 zero filler or repetition. It is efficient, though its brevity shades into under-specification rather than genuine economy.

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?

A list tool with three parameters, no output schema, and no indication of what a survey record contains or how paging works. The one-line description is not sufficient for an agent to predict the response shape or page through results confidently.

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 coverage is 33%: only organization carries a schema description (domain/slug, non-persistent, X-DeepTrue-Org fallback). The description adds no meaning for limit or offset, so their defaults and ranges (0-100) must be inferred entirely from the schema constraints.

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?

States a specific verb and resource ('List surveys') plus a scope ('in the active organization'), so an agent knows exactly what is returned. It does not distinguish itself from sibling readers such as get_survey or list_projects, leaving the listing-vs-single-record choice to be inferred from the names alone.

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 and no exclusions: nothing says to use list_surveys for enumeration and get_survey for a single record, nor when to reach for set_active_organization instead of the organization parameter. The agent must derive call choice from tool names.

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