classdesk

Umfrage anlegen oder ändern

save_survey

Ohne id: neue Umfrage (Entwurf). Mit id: nur die angegebenen Felder ändern; questions ersetzt die ganze Fragenliste. status open startet die Teilnahme per Link, closed beendet sie. Antwortet mit Link und Code.

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

Input Schema

Name	Required	Description
`id`	No
`class`	No	Klassenname, z. B. "7b" (optional; leer = ohne Klasse)
`intro`	No	Begrüßungstext vor der ersten Frage
`title`	No
`status`	No
`thanks`	No	Text nach dem Absenden
`audience`	No
`class_id`	No
`identity`	No
`questions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.7/5.0

Behavior4/5

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

While annotations are standard, the description adds crucial behavioral context that the schema lacks. It specifies the expected output (Link and Code) and the exact impact of setting the `status` to 'open' or 'closed', which are non-obvious behavioral rules.

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 dense but remarkably efficient, grouping complex rules (new vs. update, status effects, output) into concise operational statements without unnecessary filler. It is slightly dense, but not verbose.

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?

The description covers the full lifecycle understanding required for this operation: how to initiate it (new vs. existing), how to change its state (status), what results from those changes (link/code), and the specific handling of complex parameters (replacement of questions).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Given the low schema description coverage (30%), the description is highly effective at adding semantics. It explains the stateful behavior of the `id` field, the replacement nature of the `questions` array, and the operational impact of the `status` enum, which are critical rules for correct tool usage.

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 explicitly clarifies the tool's duality: it creates a new survey (when no ID is provided) or modifies an existing one (when an ID is provided). It further specifies that the `questions` parameter replaces the entire list of questions, making its purpose highly granular and unambiguous.

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?

The description provides clear operational guidelines. It dictates the difference between creation (no ID) and updating (with ID), and explains the functional consequences of the `status` field (open starts participation, closed ends it).

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

All classdesk 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?