Skip to main content
Glama

Survey results

survey_results
Read-onlyIdempotent

Returns aggregated results for one survey: response and completion counts, and per question the answer counts, average rating, NPS (promoters minus detractors) and the latest written answers. No contact identities. Free and read only. Summarize trends in plain words; do not over-read small samples. Requires API key scope: read.

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_id": "<survey_id>"
    },
    "name": "survey_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
survey_idYesSurvey id (a UUID), as returned by survey_create or surveys_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/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 covered. The description adds genuinely new behavioral context: the privacy boundary (no contact identities), that calls are free, and the required auth scope of "read" — all things an agent cannot infer from annotations or schema.

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?

Front-loaded with the return contents, then constraints, then usage advice — a sensible order with no filler. The interpretive instruction about small samples is slightly unusual but genuinely useful rather than padding.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing the return value, and it does so thoroughly: aggregate counts, per-question breakdowns, the NPS definition (promoters minus detractors), and the recency caveat on written answers. Combined with the auth and privacy notes, nothing an agent needs to call or interpret this tool is missing.

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%, and the schema already explains that survey_id is a UUID obtained from survey_create or surveys_list. The description only implies the single-survey scoping ("one survey") and adds no format, lookup, or edge-case detail beyond the schema, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ("Returns aggregated results for one survey") and then enumerates exactly what is returned: response and completion counts, per-question answer counts, average rating, NPS, and latest written answers. This is far more informative than the title and clearly separates it from stats siblings like campaign_stats.

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?

Gives clear operating context — it is read-only, free, requires the read API key scope, and returns no contact identities — plus output-handling guidance ("Summarize trends in plain words; do not over-read small samples"). It stops short of naming an alternative tool or an explicit when-not-to-use condition, so it is strong but not complete routing guidance.

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