get_intent
Fetch an intent, including fills and the post-trade report once filled. Auth required.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | intent id (uuid) |
Cofferline
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Mentions auth requirement and that fills/report are included once filled, but lacks details on side effects, errors, or further behavioral nuances. Without annotations, this is minimal but adequate for a simple fetch.
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?
Two concise sentences with no redundant information, directly conveying the essential purpose and key detail.
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?
For a straightforward getter with one parameter and no output schema, the description covers the core return contents (fills, post-trade report) and auth, though it omits edge cases like not-found scenarios. Overall adequate for its simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'id' is described identically in both schema and description, providing no additional context beyond the schema, keeping the baseline score.
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 fetches a specific intent by ID, including fills and post-trade report, distinguishing it from list_intents and other intent operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies usage for retrieving a single intent when an ID is available, but does not explicitly contrast with alternatives like list_intents or specify when not to use it.
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.8/5.0
Disambiguation5/5
Each tool targets a distinct resource and action. Within the prediction market domain, prepare vs create vs submit are clearly differentiated by signing model (client-signed vs server-signed). Even similar-sounding tools like check_spend and check_pm_order are unambiguously scoped to general spending vs PM orders, and their descriptions reinforce the boundary.
Naming Consistency5/5
All 47 tools follow a consistent verb_noun pattern with lowercase snake_case. Verbs like get, list, create, cancel, revoke, prepare, submit, set, remove, and poll are used uniformly. There is no mixing of styles or vague verbs like 'process' or 'run', making the surface highly predictable.
Tool Count2/5
47 tools is significantly above the 25-tool threshold for 'too many'. While the server covers a broad and complex domain (prediction markets, policy, delegations), the sheer count makes the surface heavy and potentially overwhelming. Some consolidation (e.g., merging related PM order operations) could reduce cognitive load without sacrificing functionality.
Completeness4/5
The tool set provides comprehensive lifecycle coverage across all major subdomains: authentication, policy versioning, delegation CRUD (prepare/confirm/list/get/revoke/renew), intent management, PM order flow (create/cancel/list/prepare/submit/check), credential management (store/list/revoke), balance and top-up operations, and account-level actions (export, offboard, panic). Minor omissions exist (e.g., no dedicated tool to view a single credential in detail or update an intent), but agents can work around these with existing tools.