Skip to main content
Glama
Sign In
Survey Solutions MCP Server

Survey Solutions MCP Server

by lbruce-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

summarize_fieldwork_status

Produce a high-level read-only summary of fieldwork progress, covering questionnaires, assignments, interviews, and user activity for quick status assessment.

Instructions

High-level read-only fieldwork summary over questionnaires, assignments, interviews, and users.

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

Input Schema

NameRequiredDescriptionDefault
profileNoOptional configured Survey Solutions profile name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

B3.2/5.0
Behavior3/5

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

The description explicitly states 'read-only', which is an important behavioral safety signal, and 'high-level' indicates an aggregated view rather than raw data. However, with no annotations present, the description carries the full burden and does not disclose output format, aggregation logic, or profile dependency.

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

Conciseness5/5

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

The description is one tight sentence with no filler. It front-loads the operation type and scope, making it immediately scannable for an agent.

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?

With no output schema and no annotations, a broad summary tool covering four entity types needs more detail about what the returned summary contains, what 'status' means, and whether the optional profile changes the scope. The description is too thin for an agent to confidently anticipate the tool's output.

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 single 'profile' parameter is already self-explanatory from the schema. The description adds no additional meaning about how the profile affects the summary, so it sits at the baseline.

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 names a specific operation (summarize), a distinguishing scope (fieldwork), and enumerates the entities covered: questionnaires, assignments, interviews, and users. It clearly distinguishes itself from more targeted sibling summaries like summarize_interviewer_activity, though 'status' remains somewhat general.

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 explicit guidance on when to choose this tool over alternatives, nor any mention of exclusions or complementary tools. The word 'high-level' hints at an overview use case, but no concrete selection criteria are given.

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