Skip to main content
Glama

Insurance guide

insurance
Read-onlyIdempotent

Information comparison of insurance kinds and insurers: what to compare besides price, with sources. No premiums, no ranking, no recommendation; Fordeal is not an intermediary.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "insurance"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoInsurance kind, e.g. havarijni; omit for all
sortNoname, rating, kinds
limitNoMax rows
detailNocompact (default) or full
localeNoLanguage, e.g. cs
offsetNoRows to skip
countryNoCountry code, e.g. CZ

Output Schema

NameRequiredDescriptionDefault
moreNoHow to fetch the next page
limitNo
totalNoAll matches, not just this page
offsetNo
returnedNo
cross_border_noteNo
commission_disclosureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "compact (default) or full",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Max rows",
      +  "type": "number"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip",
      +  "type": "number"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "commission_disclosure": {
      +      "type": "string"
      +    },
      +    "cross_border_note": {
      +      "type": "string"
      +    },
      +    "limit": {
      +      "type": "number"
      +    },
      +    "more": {
      +      "description": "How to fetch the next page",
      +      "type": "string"
      +    },
      +    "offset": {
      +      "type": "number"
      +    },
      +    "returned": {
      +      "type": "number"
      +    },
      +    "total": {
      +      "description": "All matches, not just this page",
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful non-annotation context: the output is educational comparison criteria with sources, not price data or a ranking, and Fordeal disclaims intermediary status. It says nothing about result volume, pagination, or coverage limits, which is the main remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the subject front-loaded and no filler. The semicolon-joined disclaimer clause is slightly dense, but every element (topic, caveats, legal position) carries information.

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?

With an output schema present and rich annotations, the description need not explain return values, and it correctly focuses on scope and exclusions instead. For a seven-optional-parameter read tool this is close to sufficient; a one-line pointer to the right tool for actual price comparison would close the gap.

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?

Schema description coverage is 100%, so all seven parameters (kind, sort, limit, detail, locale, offset, country) are already documented in the schema, including the one enum. The description adds no parameter-level meaning or usage examples, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (insurance kinds and insurers) and a specific angle (what to compare besides price, with sources), which is more precise than a bare 'insurance' label. It also fences off adjacent territory (premiums, ranking, recommendation), helping separate it from the 'comparisons' sibling. It stops short of explicitly naming a sibling it differs from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The exclusions ('no premiums, no ranking, no recommendation') function as when-not guidance: an agent can infer that price-lookup or ranking requests belong elsewhere. It does not name which sibling to route those requests to, so it falls short of full when/when-not/alternatives coverage.

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.

Resources