Skip to main content
Glama
Sign In

classdesk

by de.classdesk
OverviewDiscussionsAdmin

Fehlende Funktion melden

report_missing_feature

Meldet dem classdesk-Team, dass die Lehrkraft etwas wollte, das classdesk (noch) nicht kann – kein passendes Werkzeug, kein Baustein, kein Feld, keine Einstellung. Wird im Admin-Bereich gesammelt und später nachgebaut. Keine Namen von Kindern eintragen.

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": {
      "request": "<request>",
      "missing": "<missing>"
    },
    "name": "report_missing_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
missingYesWas genau in classdesk fehlt, z. B. "Baustein zum Unterstreichen von Wörtern"
requestYesWas die Lehrkraft wollte, möglichst in ihren Worten (ohne Namen von Kindern)
workaroundNoWas du stattdessen gemacht hast (oder "nichts")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare write/no-destroy/internal scope; the description adds real value on top: submissions are collected in the admin area and later built, and it imposes a privacy rule ('Keine Namen von Kindern eintragen'). It does not say what the caller sees back after submitting, but the behavioral profile is otherwise well disclosed.

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?

Three short sentences, front-loaded with the action and scope, followed by the storage consequence and the privacy rule. Nothing is redundant or padded.

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

Completeness4/5

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

For a 4-parameter submission tool with annotations and no output schema, the description covers purpose, destination, downstream handling, and the key privacy constraint. A brief note on what happens to the report immediately (confirmation/ID) would close the remaining gap.

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

Parameters4/5

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

Schema coverage is 75% (the enum-only 'area' has no prose), so the schema carries most semantics. The description still compensates usefully by reinforcing the no-names constraint that applies to the 'request' field and clarifying that the report is about an unimplemented capability, which shapes 'missing' vs 'request'.

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 ('Meldet dem classdesk-Team, dass ... etwas fehlt') and enumerates the kinds of gaps covered: no tool, no building block, no field, no setting. No sibling does anything similar, so an agent can route to it unambiguously.

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?

Gives a clear trigger condition – the teacher wanted something classdesk cannot (yet) do – which is exactly the when-to-use signal. It stops short of naming an alternative (e.g. add_support_item for support requests) or an explicit when-not-to-use, so not a 5.

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

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