Skip to main content
Glama
ngpvan-mcp

ngpvan-mcp

by Emmanuel-m42

list_survey_questions

Read-onlyIdempotent

Retrieves survey questions with their scripts and possible responses, letting you filter by name prefix and include archived questions when needed.

Instructions

Survey questions with their script and possible responses.

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

Input Schema

NameRequiredDescriptionDefault
nameNoStart of the question name
include_archivedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds only a bare mention of returned content, which the output schema already covers, and does not disclose filtering behavior, archived defaults, or other operational context.

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

Conciseness3/5

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

The description is very short and contains no filler, but it is an incomplete sentence fragment and is under-specified rather than effectively structured. It front-loads the resource but omits the action.

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 simple read-only list tool with an output schema and rich safety annotations, so it does not need detailed return-value explanation. Still, it lacks usage guidance and leaves include_archived undocumented, making the definition only minimally complete for invocation decisions.

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 50%: the name parameter is documented as a prefix match, while include_archived has no description. The tool description mentions neither parameter and therefore does not compensate for the include_archived gap.

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

Purpose3/5

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

The description identifies the resource—survey questions—and the payload fields 'script and possible responses,' but it is a noun phrase rather than an explicit verb+resource statement. It is more informative than the tool name alone yet does not clearly state the list/filter action, so it is only moderately clear.

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 statement of when to use this tool, when not to use it, or how it relates to alternatives. The schema exposes an optional name filter and archived flag, but the description gives no guidance on choosing or combining them.

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