Skip to main content
Glama

چیستارا — Iranian Legal Corpus

نرخ‌های رسمی سالانه — Look up official yearly rates

lookup_annual_rate
Read-onlyIdempotent

Fetch official Iranian yearly rates from the database: minimum wage (min_wage), court filing fees (court_fee_*), salary tax exemption (salary_tax_exemption_annual), daily severance (sanavat_daily). Delay damages and cash mahr come ONLY from calculate_delay_penalty / calculate_mahrieh — never from an index row of this table. حق‌الوکاله is NOT an annual rate — use calculate_lawyer_fee. ALWAYS use this instead of recalling a rate — yearly figures are exactly what models misremember. For دیه use calculate_diyeh instead. Read each row's unit field: «rials» means Rial and «درصد» means percent — never report a percentage as a Rial amount.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rate_type": "<rate_type>"
    },
    "name": "lookup_annual_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
rate_typeYesRate key, e.g. min_wage, court_fee_financial_first, sanavat_daily.
year_jalaliNoPersian year (optional — defaults to the latest available).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / rate_type / description
      Previous value: -"Rate key, e.g. min_wage, court_fee_financial_first, cbi_price_index, sanavat_daily."New value: +"Rate key, e.g. min_wage, court_fee_financial_first, sanavat_daily."
  2. Changed1 schema field changed
    • changedInput schema / properties / rate_type / description
      Previous value: -"Rate key, e.g. min_wage, court_fee_financial_first, cbi_price_index, lawyer_tariff_nonfinancial."New value: +"Rate key, e.g. min_wage, court_fee_financial_first, cbi_price_index, sanavat_daily."
  3. First observed

TDQS

A4.5/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, non-destructive, closed-world), so the description is free to add data-interpretation behavior instead: rows carry a `unit` field where «rials» means Rial and «درصد» means percent, with an explicit warning never to report a percentage as a Rial amount. It does not add auth, rate-limit or error behavior, so a 4 rather than 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.

Conciseness4/5

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

Purpose is front-loaded and each sentence carries a routing rule or an interpretation caveat that earns its place. Slightly dense and mildly repetitive in the 'ALWAYS use this instead of recalling' reinforcement, which keeps it just short of a 5.

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 must carry return-value guidance, and it does the most important part by explaining the `unit` field and the Rial-vs-percent trap. It still does not describe the rest of a row's shape (value, year, provenance), so it is strong but not fully complete for a 2-param lookup with no output schema.

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 description coverage is 100%, so the baseline is 3, but the description supplies additional concrete rate_type keys not present in the schema examples (court_fee_*, salary_tax_exemption_annual, sanavat_daily) and clarifies the semantics of the returned unit field. This is genuine added meaning beyond the two described parameters.

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 (fetch) and resource (official Iranian yearly rates) and enumerates the concrete keys it serves: min_wage, court_fee_*, salary_tax_exemption_annual, sanavat_daily. It explicitly differentiates itself from siblings by naming calculate_delay_penalty, calculate_mahrieh, calculate_lawyer_fee and calculate_diyeh as the correct homes for those figures.

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

Usage Guidelines5/5

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

Gives explicit when (always prefer this over recalling a rate, since yearly figures are what models misremember) and explicit when-not with named alternatives for delay damages, mahr, lawyer fees and diyeh. Nothing about tool selection is left to inference.

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.