get_fair_valueReturn one current fair value by canonical outcome id. Requires a Sorqen key. Use when the outcome id is already known; use list_fair_values for discovery.
| Name | Required | Description | Default |
|---|---|---|---|
| outcome_id | Yes |
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?
No annotations are provided, so the description carries the disclosure burden. It does add an auth requirement ('Requires a Sorqen key') and the 'current' nature of the value, but does not describe error behavior, return shape, or data freshness beyond 'current'.
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 with no filler. The primary action and parameter come first, followed by the authentication note and the alternative-tool routing.
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 one-parameter lookup tool, the description covers purpose, parameter semantics, auth, and the alternative. It omits output structure and error conditions, but the simplicity and title reduce the impact of those gaps.
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 0% for the single parameter, so the description must compensate. It conveys that outcome_id is canonical and already known, which adds meaning beyond the bare schema type, but it does not describe format, source, or examples.
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 action ('Return'), resource ('one current fair value'), and the key identifier ('canonical outcome id'). It clearly distinguishes itself from list_fair_values and get_fair_value_history by targeting a single current value by known id.
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?
Explicitly directs when to use this tool ('when the outcome id is already known') and when to use the sibling ('use list_fair_values for discovery'). This is clear routing guidance with no ambiguity.
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.