bani_einordnung
Erklärt das BANI-Modell und seine vier Dimensionen mit Führungskonsequenzen und Kapitelverweisen.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
leadership-agent
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It indicates the tool explains a model (likely read-only), but does not mention side effects, safety, or limitations. Basic transparency is achieved but no extra context.
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?
The description is a single sentence, front-loaded, and contains no extraneous information. Every word adds value, making it appropriately concise.
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?
Given the low complexity (no parameters, no output schema), the description covers the main purpose and content. It could mention the return format or that it's informational, but completeness is adequate.
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?
Tool has zero parameters and schema coverage is 100%. Description adds no parameter-specific meaning, but this is acceptable since no parameters exist. Baseline for 0 parameters is 4.
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 clearly states the tool explains the BANI model, its four dimensions, leadership consequences, and chapter references. It specifies a specific resource and verb, distinguishing it from siblings like glossar or kapitel_these.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidelines are provided. The description does not mention when to use this tool versus alternatives or provide any contextual cues for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.6/5.0
Disambiguation4/5
Each tool has a clear, distinct purpose: BANI model explanation, experiment status, glossary definition, chapter overview, and emergency impulse. Only minor overlap between BANI explanation and glossary if both cover BANI, but they are structured differently.
Naming Consistency4/5
All tool names follow snake_case and use descriptive compound nouns (e.g., 'bani_einordnung', 'notfall_griff'). While not verb_noun, the pattern is consistent and predictable.
Tool Count5/5
5 tools is well-scoped for a specialized leadership agent, covering core functionalities without being excessive or insufficient.
Completeness3/5
The set covers definitions, model explanation, chapter navigation, and acute situation help, but lacks a general question-answering or coaching tool, leaving a notable gap for broader leadership support.