Skip to main content
Glama

Dadras — Iranian law (دادرس)

Search Iranian law (دادرس)

search_iranian_law
Read-onlyIdempotent

Search the text of Iranian statutes and regulations (قوانین و مقررات) published by Dadras — over 95,000 articles of more than 5,900 laws — and get the best-matching articles, each with an excerpt of its text, a note when it is repealed or old, and its dadrasai.com link. Use it for a question about what Iranian law says on a subject — «شرایط فسخ قرارداد اجاره», «مجازات کلاهبرداری» — or to check an article's wording before quoting it. Not for reading one known article in full (get_law_article), finding a law by its name (find_law), a word's meaning (explain_legal_term) or an amount (the calculate_* tools). Covers statutes and regulations only, not court rulings. Candidates are ordered by a legal relevance model; an article named by number and law comes first. Works best in Persian, in the statute's own vocabulary rather than as a story.

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": {
      "query": "<query>"
    },
    "name": "search_iranian_law"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many articles to return (1–8); 5 when not given.
queryYesA Persian search phrase of a few words — the legal subject («حضانت فرزند پس از طلاق») or an article («ماده ۱۰ قانون مدنی»); English works less well.

Output Schema

NameRequiredDescriptionDefault
textYesThe result, in Persian, as it should be quoted.
linksYesThe dadrasai.com pages the result cites, in order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"How many articles to return (1–8)."New value: +"How many articles to return (1–8); 5 when not given."
    • changedInput schema / properties / query / description
      Previous value: -"Persian search phrase, e.g. «حضانت فرزند پس از طلاق»."New value: +"A Persian search phrase of a few words — the legal subject («حضانت فرزند پس از طلاق») or an article («ماده ۱۰ قانون مدنی»); English works less well."
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many articles to return (1–8)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "links": {
      +      "description": "The dadrasai.com pages the result cites, in order.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "text": {
      +      "description": "The result, in Persian, as it should be quoted.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "text",
      +    "links"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds substantial context beyond them: what each result includes (excerpt, repeal/age note, link), the ranking model ('legal relevance model', with an article named by number and law ranked first), the language expectation, and the corpus boundary. This is rich disclosure for a search tool.

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?

It is a single dense paragraph, but front-loaded with purpose and results, then usage, then exclusions, then ranking behavior — every sentence carries information. Slightly long, yet no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, yet the tool covers scope, alternatives, ranking rationale, and language/query style. Nothing an agent needs to invoke it correctly is missing.

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 the baseline is 3, but the description adds query-formulation guidance beyond the schema: target the statute's own vocabulary rather than a narrative, use Persian, and expect article-number-style queries (e.g. «ماده ۱۰ قانون مدنی») to rank first. `limit` is left entirely to the schema, which already documents the 1–8 range.

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 (search) and resource (text of Iranian statutes and regulations published by Dadras) with concrete scale (95,000+ articles across 5,900+ laws) and what each result contains (excerpt, repealed/old note, dadrasai.com link). It clearly differentiates itself from siblings like get_law_article and find_law by naming them in the negative space.

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?

Explicitly states when to use it ('a question about what Iranian law says', 'check an article's wording before quoting') and when not to, naming each alternative tool for the excluded cases (get_law_article, find_law, explain_legal_term, the calculate_* tools). It also scopes the corpus ('statutes and regulations only, not court rulings').

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