Skip to main content
Glama

Dadras — Iranian law (دادرس)

by com.dadrasai
OverviewDiscussionsAdmin

Find an Iranian law by name

find_law
Read-onlyIdempotent

Find Iranian laws and regulations by their title, or part of it, in Dadras's library: up to 10 matches, best first, each with its slug, number of articles and dadrasai.com page. Use it when the user names a law («قانون صدور چک», «مدنی») and its exact title or slug is needed, before list_law_articles. It matches title words only; to find what laws say about a subject, use search_iranian_law.

Input Schema

NameRequiredDescriptionDefault
nameYesAll or part of the law's Persian title; a distinctive word works best, e.g. «مدنی» or «صدور چک».

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. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"All or part of the law's Persian name, e.g. «مدنی» or «صدور چک»."New value: +"All or part of the law's Persian title; a distinctive word works best, e.g. «مدنی» or «صدور چک»."
  2. Changed2 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"All or part of the law's Persian name, e.g. «مدنی» or «صدور چک»."
    • 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.7/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's added value is the result behavior: a cap of 10 matches, best-first ordering, per-match fields (slug, article count, dadrasai.com page), and the title-words-only matching rule. It stops short of describing behavior on zero matches or partial-word handling, but the disclosure is well beyond the annotations.

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?

Three dense sentences, front-loaded with the core action and result shape, followed by usage conditions and the disambiguation rule. Every sentence carries distinct information with no repetition of the title.

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?

For a one-parameter lookup with an output schema already present, the description covers purpose, trigger, result cardinality and ordering, matching semantics, and sibling routing. An agent has everything needed to select and call it correctly.

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% for the single parameter, so the baseline is 3. The description nonetheless adds meaning the schema lacks: matching is against title words only, so an agent learns that a topic string or full-text query will not work here and that partial/distinctive words are the intended input style.

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?

The description states a specific verb and resource (find Iranian laws/regulations by title or partial title) and explicitly distinguishes itself from the two closest siblings: list_law_articles and search_iranian_law. An agent can pick it without opening any schema.

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?

It names the triggering condition ('when the user names a law'), gives concrete examples, states the exclusion ('matches title words only; to find what laws say about a subject, use search_iranian_law'), and specifies sequencing ('before list_law_articles'). Nothing 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.

All Dadras — Iranian law (دادرس) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources