Skip to main content
Glama
Sign In
Survey Solutions MCP Server

Survey Solutions MCP Server

by lbruce-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

generate_tablet_setup_instructions

Generate tailored tablet setup instructions from workspace, server, and interviewer details to guide field teams through configuration.

Instructions

Generate practical tablet setup instructions from workspace/server/user details.

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": {
      "workspace_name": "<workspace_name>"
    },
    "name": "generate_tablet_setup_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNo
workspace_nameYes
interviewer_usernamesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

C2.7/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 full burden of behavioral disclosure. It does not state whether the operation is read-only, what output format is produced, what permissions are needed, or whether any side effects occur.

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?

The description is a single, front-loaded sentence with no filler or redundant phrasing. Every word contributes to the general purpose, though significant detail is missing in other dimensions.

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?

For a generation tool with no output schema, no annotations, and zero parameter-level documentation, this description is incomplete. An agent would not know what the generated instructions look like, how to interpret the inputs, or what results to expect.

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 0%, so the description must compensate for parameters like profile, workspace_name, and interviewer_usernames. It only loosely refers to 'workspace/server/user details' and does not explain what 'profile' means or how interviewer_usernames affect the generated instructions.

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 specific verb and resource: 'generate practical tablet setup instructions' from workspace/server/user details. This makes the tool's purpose reasonably clear and distinguishes it from siblings like generate_fieldwork_brief, though it does not explicitly contrast with them.

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 on when to use this tool versus alternatives such as generate_fieldwork_brief or setup_questionnaire_fieldwork_project. The description implies a purpose but provides no when-to-use or when-not-to-use context.

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