Skip to main content
Glama

scobees_me

Displays your scobees account details (ID, role, school), verifies login status, and checks whether the scobees version matches the server-tested version.

Instructions

Zeigt das eigene scobees-Konto (ID, Rolle, Schule), prüft die Anmeldung und vergleicht die scobees-Version mit der, für die dieser Server geprüft wurde.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does convey that this is a read-only inspection (zeigt/prüft/vergleicht) with no side effects, plus the non-obvious version-compatibility behavior. It stops short of saying whether a version mismatch returns an error, a warning flag, or a boolean, and gives no indication of failure modes for unauthenticated calls.

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?

A single sentence that front-loads the primary value (account identity) and then adds the secondary checks. No filler. It is dense but reads naturally in one pass.

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 zero-parameter, no-output-schema tool, the description covers what is returned (ID, role, school) and the extra version-comparison outcome. The only real gap is the shape of the version-check result, which an agent would want in order to act on a mismatch.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing parameter-level to explain and the description correctly spends no words on inputs.

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

Purpose4/5

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

The description names three concrete operations on a named resource: showing the own account (ID, role, school), verifying login, and comparing the scobees version against the server's validated version. This is specific and clearly distinct from the content-oriented siblings (list/get/create/update). It does not explicitly name a sibling to route away from, which keeps it below 5.

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

Usage Guidelines3/5

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

Usage is strongly implied — this is the whoami/login-check tool an agent would call first to confirm authentication and compatibility — but the description never states when to call it versus alternatives, nor what to do if the version check fails. Adequate but inferential.

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