describe_methodsDescribe the versioned fair-value method and refusal philosophy. No API key required. Use it to interpret Sorqen numbers; use list_fair_values for current data.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden, and it discloses the key auth trait ('No API key required'). 'Describe' implies a non-mutating information operation, so the absence of side-effect disclosure is not a major gap. It does not describe the output format, but this is a minor omission for a simple explanatory tool.
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 sentences, front-loaded with the core purpose and immediately followed by the alternative. Every clause earns its place and no redundant schema information is repeated.
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 no-parameter, no-output-schema explanatory tool, the description is complete: it says what it describes, that no auth is needed, and when to prefer a sibling. An agent has enough information to decide whether to call it.
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 has zero parameters, so there are no parameter semantics to document. The description's 'No API key required' note is not parameter documentation but removes a potential confusion about required inputs.
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?
The description states a specific verb ('Describe') and a specific resource ('versioned fair-value method and refusal philosophy'), and the second sentence distinguishes it from list_fair_values by saying the latter is for current data. This clearly identifies the tool's scope relative to its siblings.
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?
It provides explicit usage guidance: use this tool to interpret Sorqen numbers and use list_fair_values for current data. This gives an agent a clear decision rule for choosing between two otherwise similar tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: describe_* covers meta topics, list_* covers discovery, get_* covers retrieval, and grade is a unique action. The descriptions explicitly cross-reference when to use one tool vs another, such as list_fair_values for discovery and get_fair_value for known outcome ids.
Tool names are overwhelmingly consistent snake_case imperative verb_noun pairs (describe_, get_, list_), and grade is a readable verb-only command. The single deviation from verb_noun is minor and does not create confusion.
Ten tools is well-scoped for the server's purpose: meta/explanation tools, discovery tools, retrieval tools, and a grading action. Each tool earns its place without overlapping or feeling like filler.
The tool surface covers the full read-only workflow: discover supported leagues, list and fetch fair values, retrieve history, grade submitted prices, and understand settlement rules, plans, and authentication. There are no obvious dead ends or missing operations for the stated domain.