Skip to main content
Glama
Sign In
Survey Solutions MCP Server

Survey Solutions MCP Server

by lbruce-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_statistics_report

Fetch a built-in Survey Solutions statistics report by passing query parameters to filter results for analysis.

Instructions

Read a built-in Survey Solutions statistics report using query parameters.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It only indicates the operation is a read, but it does not disclose the response shape, pagination behavior, required permissions, or whether the report content depends on the active profile or workspace.

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

Conciseness2/5

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

The description is a single short sentence with no wasted words, but it is under-specified rather than usefully concise. It skips essential detail that an agent needs to select and invoke the tool correctly.

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

Completeness1/5

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

With no output schema, no annotations, and a generic query parameter, the description is far from complete. It does not explain what report is returned, how to build the query, what profile means, or how the result relates to sibling statistics tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has two parameters, 'query' and 'profile', with 0% schema description coverage. The description merely says 'using query parameters' and adds no meaning to either parameter, leaving an agent with no idea what keys the query object should contain or how 'profile' is used.

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 clear verb and resource: 'read a built-in Survey Solutions statistics report.' It is understandable at a high level, though it does not specify which built-in report or how it differs from closely related siblings like list_statistics_questionnaires or get_interview_stats.

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 about when to use this tool versus the many statistics-related siblings. The phrase 'using query parameters' hints at some flexibility but provides no context, prerequisites, or alternatives.

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

Deploy Server

Other Tools