iran-insurance-mcp

Overview Schema Source Related Servers Discussions Admin

Find insurer claim centers

ins_claim_centers

Read-onlyIdempotent

Locate insurers' damage-claim branches by insurer, city, province, and claim type, returning addresses, phone numbers, and map positions for claim visits.

Instructions

Find insurers' damage-claim branches with address, phone numbers and map position, filtered by insurer, place and claim type.

BimeBazar only. Get insurer and place values from ins_insurers and ins_places first. Check total against 5 per page.

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

Input Schema

Name	Required	Description
`city`	No	City value from ins_places, e.g. 'karaj'.
`page`	No	1-based page, 5 centers each.
`company`	No	Insurer url_name from ins_insurers, e.g. 'iran'.
`service`	No	Claim type: third-party injury, third-party property, car body.
`province`	No	Province value from ins_places, e.g. 'tehran'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv0.2.0Nov 6, 2026

removedInput schema / properties / city / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

changedInput schema / properties / city / description

Previous value: -"City value from ins_places (BimeBazar side), e.g. 'karaj'."New value: +"City value from ins_places, e.g. 'karaj'."

addedInput schema / properties / city / type

Added value: +[
+  "string",
+  "null"
+]

removedInput schema / properties / company / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

changedInput schema / properties / company / description

Previous value: -"Insurer url_name from ins_insurers (BimeBazar side), e.g. 'iran'."New value: +"Insurer url_name from ins_insurers, e.g. 'iran'."

addedInput schema / properties / company / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / province / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

changedInput schema / properties / province / description

Previous value: -"Province value from ins_places (BimeBazar side), e.g. 'tehran'."New value: +"Province value from ins_places, e.g. 'tehran'."

addedInput schema / properties / province / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / service / anyOf

Removed value: -[
-  {
-    "enum": [
-      "thirdparty_life",
-      "thirdparty_financial",
-      "carbody"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

changedInput schema / properties / service / description

Previous value: -"Claim type the branch handles: third-party injury, third-party property, car body."New value: +"Claim type: third-party injury, third-party property, car body."

addedInput schema / properties / service / enum

Added value: +[
+  "thirdparty_life",
+  "thirdparty_financial",
+  "carbody",
+  null
+]

addedInput schema / properties / service / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedv0.1.2Nov 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, and the description still adds value: a fixed page size of 5, the existence of a `total` field in the response, and the "BimeBazar only" data-source constraint. It does not cover rate limits or empty-result behavior, which keeps 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 paragraphs, both front-loaded: the capability and return fields come first, then the operational preconditions. No sentence is filler — even the return-field list earns its place because no output schema exists.

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 no output schema, the description compensates by naming the returned fields and the `total` counter, and the mandatory lookup chain is spelled out. What remains thin is what happens when a filter combination yields nothing and whether filters are combinable, but overall it is sufficient for correct invocation.

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 coverage is 100% and each parameter already documents its source tool and example value (e.g. 'karaj' from ins_places, url_name from ins_insurers), so the schema is doing the heavy lifting. The description only restates the filter groupings at a high level without adding format or combination rules, which is the baseline 3.

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?

Uses a specific verb ("Find") with a precisely scoped resource ("insurers' damage-claim branches") and enumerates both the returned fields (address, phone numbers, map position) and the filter dimensions (insurer, place, claim type). This makes it clearly distinguishable from the sibling quote and lookup tools, which do not return branch contact data.

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?

Gives explicit prerequisites ("Get insurer and place values from ins_insurers and ins_places first") and a pagination rule ("Check `total` against 5 per page"), which is strong when-to-use guidance. It stops short of stating when-not to use it or naming an alternative, but no sibling overlaps functionally, so the practical gap is small.

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

Deploy Server