Skip to main content
Glama
sepehr071

doctoreto-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Insurances

dt_insurances
Read-onlyIdempotent

List Iranian basic and supplementary insurers and their IDs so you can filter doctor searches by accepted insurance.

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 search a lot; centers list theirs in dt_center.

Input Schema

NameRequiredDescriptionDefault
limitNoMax insurers (about 84 exist).
queryNoPart of the insurer's name in Persian, e.g. 'تامین' or 'آتیه'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), yet the description adds real behavior: `total` counts all matches (relevant since there is no output schema) and the domain fact that few doctors list insurances, so filtering narrows results sharply. That is useful context beyond the structured fields, though pagination/limit interaction is not discussed.

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?

Front-loaded with the verb+resource and the downstream link, then two short supporting sentences with no filler. Slightly clipped phrasing ('the ids dt_search_doctors(...) takes') costs a little readability but nothing is wasted.

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 simple two-parameter, no-output-schema lookup, the description supplies the missing pieces: the `total` return field and the reason the filter matters. It is essentially complete for correct invocation, with only limit/pagination behavior left implicit.

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%, with limit (max 200, ~84 exist) and query (Persian name fragment, examples) already fully documented. The description adds nothing about the parameters themselves, so the baseline 3 applies.

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?

States a specific verb (List) and resource (basic and supplementary insurers) and immediately ties it to its downstream consumer, dt_search_doctors(insurance_ids=...). It also explicitly differentiates from dt_center for centers, so the agent can place it among siblings without opening a schema.

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?

Makes the use case concrete by naming the parameter the returned ids feed into (insurance_ids on dt_search_doctors) and routes centers to dt_center. It stops short of an explicit when-to-use/when-not statement or a note on when the filter is worth applying versus searching without it.

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

Deploy Server

Other Tools