Skip to main content
Glama
Sign In
Survey Solutions MCP Server

Survey Solutions MCP Server

by lbruce-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_questionnaire_criticality_level

Retrieve the criticality level of a questionnaire from Survey Solutions Headquarters to assess its importance and guide further actions.

Instructions

Read questionnaire criticality settings where supported by the active Headquarters build.

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": {
      "questionnaire_identity": "<questionnaire_identity>"
    },
    "name": "get_questionnaire_criticality_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNo
questionnaire_identityYesQuestionnaire identity in GUID$Version format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

A3.8/5.0
Behavior3/5

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

There are no annotations, so the description carries the behavioral disclosure burden. It clearly states that this is a read operation and adds a feature-availability caveat, but it does not describe the output shape, error behavior when unsupported, or any permission requirements. For a simple getter, this is adequate but not rich.

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 a single sentence that states the action, the resource, and the key availability condition. Every word contributes, and it is appropriately front-loaded with the verb and object.

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

Completeness3/5

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

This is a low-complexity read tool, but with no output schema and no annotations, the agent is missing information about the return value and the meaning of the optional profile parameter. The description is not misleading but is not fully complete for a tool with an undocumented parameter and no output specification.

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 description coverage is only 50%; questionnaire_identity is documented as 'GUID$Version format', but the optional profile parameter has no schema description. The tool description does not compensate by explaining what profile means or how it affects the read, leaving the agent to guess about half the parameters.

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?

The description uses a specific verb ('Read') and resource ('questionnaire criticality settings'), making the tool's function immediately clear. It also adds a scoping condition ('where supported by the active Headquarters build') that distinguishes it from its write sibling set_questionnaire_criticality_level.

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?

The description provides clear context by framing this as a read operation conditioned on Headquarters build support. It does not explicitly name alternatives or exclusions, but the read versus set distinction is implicit from the sibling tools and the verb choice.

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