Skip to main content
Glama

Insurances

dt_insurances
Read-onlyIdempotent

Lists basic and supplementary Iranian insurers with the IDs needed to filter doctor searches by insurance; use the optional Persian-name query to find and select insurer IDs.

Instructions

List basic and supplementary insurers with the ids dt_search_doctors(insurance_ids=...) takes.

total counts all matches. Few doctors list insurances, so the filter narrows a lot.

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": "dt_insurances"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax insurers.
queryNoPart of Persian name, e.g. 'تامین'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max insurers (about 84 exist)."New value: +"Max insurers."
    • removedInput schema / properties / query / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 50,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / query / description
      Previous value: -"Part of the insurer's name in Persian, e.g. 'تامین' or 'آتیه'."New value: +"Part of Persian name, e.g. 'تامین'."
    • addedInput schema / properties / query / maxLength
      Added value: +50
    • addedInput schema / properties / query / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed4 schema fields changedv0.3.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 100,
      +  "description": "Max insurers (about 84 exist).",
      +  "maximum": 200,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"dt_insurancesArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dt_insurancesDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: that `total` counts all matches (not just the returned page) and that insurance coverage is sparse among doctors, which affects result expectations. It does not discuss limit/pagination behavior, keeping it below a 5.

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 short sentences, no filler, and the most decision-relevant fact (what the ids feed into) is front-loaded. The `total` clarification follows directly and nothing is repeated from the schema or annotations.

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 two-optional-parameter read-only lookup with no output schema, this covers purpose, downstream use, result-count semantics and filter selectivity — enough to call it correctly. Minor gap: it does not say whether an empty `query` returns everything or how to page past the 200-item cap, though the schema constrains those values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both `limit` and `query` are already documented, making 3 the baseline. The description adds real meaning on top by tying the output ids to dt_search_doctors's insurance_ids parameter, which the schema cannot express, and by clarifying what `total` represents.

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?

Names a specific verb and resource ("List basic and supplementary insurers") and immediately states what the returned ids are for — they are the values dt_search_doctors(insurance_ids=...) accepts. That cross-tool framing distinguishes it cleanly from siblings like dt_specialities and dt_cities, which are parallel lookup tables with no such note.

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?

Usage is clearly implied: call this first to obtain insurance ids, then pass them to dt_search_doctors. The note that "few doctors list insurances, so the filter narrows a lot" warns the agent that the filter is high-selectivity. It stops short of explicit when-not guidance or naming an alternative path, so it is not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.