Look up Stellaris slang and abbreviations to decode community shorthand that new players may not know, with a random glossary sample when no term is provided.
Look up Stellaris slang and abbreviations (FE, AE, GC, ecum, naval cap, tall/wide, CG...). Explains community shorthand a new player will not know.
| Name | Required | Description | Default |
|---|---|---|---|
| term | No | Slang or abbreviation. Leave empty for a random sample of the glossary. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the burden; it implies a safe read-only lookup and explains it returns explanations, but never explicitly states read-only behavior, whether results are cached/static, or response shape. Adequate for a low-risk glossary, but thin.
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?
Two tight sentences, front-loaded with purpose and backed by useful examples; nothing redundant or wasted.
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?
For a zero-required-parameter glossary with a single well-documented argument and no output schema, the definition supplies enough for an agent to call it correctly. It could say a bit more about return format, but little is missing.
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?
Schema coverage is 100% and the schema already documents that empty input yields a random sample. The description adds only illustrative term examples, not new semantics for the term argument.
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 ('Look up Stellaris slang and abbreviations') with concrete examples (FE, AE, GC, ecum, tall/wide, CG) that make the scope unambiguous. It distinguishes itself from generic siblings like stellaris_search by being a glossary, though it does not explicitly name or contrast with stellaris_explain.
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?
The phrase 'community shorthand a new player will not know' implies when to reach for it, but there is no explicit when-to-use/when-not or pointer to an alternative such as stellaris_explain. 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.