QuestionPunk

Skill List

skill_list

Read-onlyIdempotent

List the analysis skills the user can run: QuestionPunk's built-ins (executive-summary, segment-comparison, key-themes, recommendations) and the skills the user and their teams saved, each with its prompt and whether the user may edit it. With surveyId, also returns segmentQuestions: the questions segment-comparison can group that survey's respondents by. Also returns the user's teams, for sharing a skill. To run a skill, use skill_prompt and analyze the answers yourself (free); skill_run has QuestionPunk's AI run it instead.

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

Input Schema

Name	Required	Description	Default
`surveyId`	No	Survey ID (from survey_list), to get the questions segment-comparison can group by

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond that: each skill comes with its prompt and an editable flag, and the response also includes the user's teams for sharing purposes.

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?

Front-loads the core action and return contents, then closes with a clear alternative-tool routing sentence. Dense but nearly every clause carries information; the parenthetical built-in list is long but useful for recognition.

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

Completeness5/5

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

An output schema exists, yet the description still signals the key return fields (prompt, editable flag, segmentQuestions, teams), which is enough for an agent to call this correctly. Nothing needed to invoke the tool is missing.

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 coverage is 100% and the surveyId schema entry already says it retrieves the questions segment-comparison can group by. The description restates essentially the same meaning with slight elaboration, so it lands at the baseline rather than adding new semantics.

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?

States a specific verb and resource ("List the analysis skills the user can run") and enumerates both sources: QuestionPunk built-ins (executive-summary, segment-comparison, key-themes, recommendations) and user/team-saved skills. It also names the sibling tools skill_prompt and skill_run so the agent can distinguish listing from running.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes between alternatives: use skill_prompt and analyze answers yourself (free) versus skill_run for QuestionPunk's AI. It also states the conditional use of surveyId to additionally retrieve segmentQuestions, leaving no ambiguity about when to pass it.

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

All QuestionPunk tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?