get_sla_history
Returns the full SLA history for a wallet address.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| wallet | Yes | Wallet address (0x...) |
InsureLink
TDQS
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosing behavioral traits. It states that the tool returns full SLA history, but does not mention any pagination, auth requirements, potential size, or what 'full' implies. It implicitly reads as a read-only operation, but lacks deeper transparency.
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?
The description is a single sentence with no redundant wording. It is appropriately sized for the tool's simplicity and immediately communicates the primary function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple one-parameter schema, the description is minimally adequate, but there is no output schema and no annotations. The description does not explain the structure/format of the returned SLA history or any limitations, which would improve completeness. It meets the minimum viable bar but leaves room for more detail.
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 input schema already describes the sole parameter 'wallet' as 'Wallet address (0x...)' with 100% coverage. The description does not add any additional meaning beyond what the schema provides, so the baseline score of 3 is appropriate.
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 'Returns the full SLA history for a wallet address' clearly identifies the action (returns), the resource (SLA history), and the scope (wallet address). This distinguishes it from sibling tools like get_activity or get_agent_claim_history by focusing on SLA-specific history.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives among the many sibling tools. There are no exclusions, prerequisites, or context cues, leaving the agent to infer usage solely from the name and one-sentence description.
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.5/5.0
Disambiguation3/5
Many tools have similar purposes, such as the three simulation tools (simulate_action, simulate_paid_action, simulate_paid_action_batch) and the two payment wrappers (pay_then_call, insurelink_charge). While descriptions clarify distinctions, an agent may struggle to choose correctly without careful reading.
Naming Consistency5/5
All tool names use lowercase snake_case with a consistent verb_noun or verb_noun_noun pattern (e.g., get_reputation, subscribe_attestation_freshness). No mixing of conventions or styles.
Tool Count2/5
With 28 tools, the surface is larger than typical. While each tool serves a specific function, many could be consolidated (e.g., simulation tools, payment wrappers) to reduce cognitive load. The count exceeds the 25-tool threshold for 'too many'.
Completeness3/5
Core operations for reputation, attestation, SLA lifecycle, and payments are present. However, gaps exist: no tool to list individual SLAs or update an SLA beyond renewal/reset, and no dispute or pricing query tool. The set covers the domain but has notable missing operations.