Displays your scobees account details (ID, role, school) and checks login status. Use it to verify authentication before creating or extending learning paths.
Zeigt das eigene scobees-Konto (ID, Rolle, Schule) und prüft die Anmeldung.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden alone. 'Zeigt' and 'prüft' convey a read-only, non-mutating operation and name the returned fields, but nothing is said about error behavior on failed authentication or whether the call is idempotent/cached.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that front-loads the identity information and appends the authentication check. No redundant restatement of the name or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description must convey the shape of the result; it names three key fields but not the full payload, and it leaves open what an unauthenticated response looks like. Adequate for a simple tool, but not complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to document; the baseline for a parameterless tool applies. The description appropriately spends its words on scope and returned fields instead of parameter detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: shows the caller's own scobees account and lists the fields returned (ID, Rolle, Schule). It is clearly distinct from the content-oriented siblings (list_lernpfade, create_aufgabe, etc.), though the distinction is implicit rather than called out.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'prüft die Anmeldung' implies a sensible use case — verifying credentials/identity before other calls — but the description never says when to prefer this over alternatives or what to do if the check fails. Usage is inferable but not spelled out.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.