list_carriersDemo tool — list simulated carriers registered in the ParaSure demo environment. Returns a carrier name, supported perils, regions, and products. No payment is accepted; the only listed carrier is simulated and live carrier integrations are not yet available.
| 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?
Beyond the readOnlyHint annotation, the description adds valuable context: it's a demo tool, only one simulated carrier exists, no payment is accepted, and live integrations are not available. This helps set expectations about data quality and scope, which the annotation alone does not convey.
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 concise sentences with no fluff. The core purpose and key constraints are front-loaded, and every sentence adds information. It is well-structured and scannable.
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 demo tool without an output schema, the description covers what it returns, the simulation nature, and payment restrictions. It lacks details like pagination or response format, but these are less critical for a simple demo list tool. A 4 is appropriate.
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 no parameter explanation is needed. The baseline for zero parameter tools is 4, and the description doesn't need to add anything further.
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 clearly states the action ('list') and the resource ('simulated carriers registered in the ParaSure demo environment'), and distinguishes it from the mutating and quoting sibling tools. It also specifies the return fields (carrier name, perils, regions, products), making the purpose unambiguous.
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?
No explicit guidance on when to use this tool versus alternatives. The description hints at a demo/read-only context but does not mention when to prefer it over, say, get_parametric_quote or check_trigger. It lacks 'when not to use' clauses.
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 serves a distinct role in the parametric insurance workflow: risk assessment, quoting, binding, trigger checking, policy status, and carrier listing. There is no overlap or ambiguity in purpose, and the entry point is clearly marked.
All tool names follow a consistent verb_noun snake_case pattern (assess_weather_risk, bind_policy, check_trigger, get_parametric_quote, get_policy_status, list_carriers). No mixed conventions or irregularities.
Six tools is well-scoped for a demo parametric insurance server, covering the essential lifecycle steps without redundancy or unnecessary expansion. Each tool has a clear purpose.
The tool set covers the primary flow: assess risk, get quote, bind policy, check trigger, and retrieve status. It lacks update/cancel policy operations, but for a demo environment focused on quoting and triggering, this is a minor gap.