get_settlement_rulesReturn Sorqen settlement-context rules and tie prior used by the local client comparison path. Requires a Sorqen key. This is context, not a venue market feed.
| 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?
No annotations are provided, so the description carries the behavioral disclosure burden. It discloses an authorization prerequisite (Sorqen key) and the nature of the data (context, not market feed), which is meaningful. It does not describe return format, side effects, or error behavior, but for a zero-parameter lookup this is a modest gap.
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?
The description is two sentences with no filler. The first sentence states the action and object; the second adds a prerequisite and a category disclaimer. Every clause earns its place.
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-parameter context tool with no output schema, the description states what it returns, its auth requirement, and its intended use case. It does not elaborate on the shape of the returned rules, but the tool is simple and sibling tools provide contrast. Overall, the essential guidance is present.
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 the baseline is 4; there are no parameter semantics for the description to clarify. The schema coverage of 100% is vacuous, and the description adds the relevant non-parameter context (auth key).
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 uses a specific verb ('Return') and names a concrete resource ('Sorqen settlement-context rules and tie prior'), and clarifies its role as context for the local client comparison path. The closing sentence explicitly differentiates it from a venue market feed, which helps an agent avoid confusing it with data-feed tools. However, it does not explicitly name a sibling tool, so differentiation is by category rather than direct comparison.
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 states the required precondition ('Requires a Sorqen key') and situates the tool within a specific path ('local client comparison path'). It also gives exclusion guidance by saying it is 'context, not a venue market feed.' It does not explicitly list sibling tools or say 'use X instead,' but the intended context is clear enough.
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.