Finish wallet sign-in: exchanges the signed SIWE message for a cl_sess_… session token — use it as the Authorization bearer on every authenticated tool. Free, no auth.
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | the exact SIWE message from start_siwe_login | |
| signature | Yes | the wallet's signature over the message, 0x… |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses that the tool is 'Free, no auth' and that it produces a session token for subsequent authenticated calls. It does not mention token expiry or invalidation of prior sessions, but for a login completion step this is reasonably transparent.
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 verb phrase, and no filler. Every clause adds value: the action, the output, the token usage, and the cost/auth status.
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 two-parameter, no-output-schema tool, the description fully covers the workflow: it explains the input origin, the output token, and how to use the result. No significant information gap remains.
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 schema already describes both parameters accurately and completely (100% coverage), so the baseline is 3. The description mentions the 'signed SIWE message' but adds little about the signature parameter beyond what the schema provides.
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 opens with 'Finish wallet sign-in' and immediately specifies the action: 'exchanges the signed SIWE message for a cl_sess_… session token'. This clearly distinguishes the tool from its sibling start_siwe_login, which initiates the sign-in flow.
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 description implies when to use it ('Finish wallet sign-in') and gives post-use guidance ('use it as the Authorization bearer on every authenticated tool'). It does not explicitly name alternatives or state when not to use, but the reference to a signed SIWE message makes the prerequisite and context clear.
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 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.
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.
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.
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.