qavanin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QAVANIN_MCP_PROXY | No | Optional HTTP proxy for requests to qavanin.ir. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qv_lawA | Read the full text of a law, regulation, court vote or opinion as sections (articles, notes, headings). Each section has |
| qv_law_infoA | Metadata of a law: type, approving body, approval, notification and gazette dates and numbers, last status, effective date, executing bodies and recipients of the copy. Use after qv_search to cite a law ("approved 1318/..., published in gazette no. ...") or to check its type. Court votes and opinions carry almost no metadata. Dates are Jalali. |
| qv_amendmentsA | Which laws amended this one, which this one amends, and which of its articles were amended. Returns |
| qv_article_historyA | Every amendment of one article: type (اصلاحی...), date, the amending law and the replacing text. Use after qv_law or qv_amendments when asked how an article changed. Oldest change first. An article that was never amended returns an empty list. |
| qv_relatedA | Documents related to a law: other laws, and regulations, court votes and legal opinions that cite or interpret it (hundreds for the civil code, newest first). Returns |
| qv_searchA | Search the Iranian law and regulation database (qavanin.ir, 168,000 documents) and list matching titles. Returns total hits, page count and items with |
| qv_lookupA | Find the ids that qv_search filters take: approving bodies, executing bodies, subjects, types, statuses, lists. Returns items with |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct aspect: search, filter-id lookup, full text, metadata, amendment relationships, per-article history, and related documents. The only real overlap is between qv_amendments (summary of which laws amended this one) and qv_article_history (full history of one article), but the descriptions explicitly cross-reference each other to clarify the boundary.
All tools share a consistent 'qv_' prefix and readable snake_case suffixes, giving a predictable family. However, the convention mixes verbs (qv_lookup, qv_search) with nouns (qv_law, qv_law_info, qv_amendments, qv_related), so it is mostly rather than fully consistent.
Seven tools is well-scoped for a read-only legal database, with each tool earning its place by covering a distinct layer (search, lookup, read, metadata, amendments, history, relations). No redundant or filler tools are present.
The surface covers the full read lifecycle of a law: find it, resolve filter ids, read its text, get metadata, trace amendments and related documents. Since the server is read-only over an external corpus, CRUD is not expected; minor gaps like a direct citation/formatter or bulk-export tool remain but are workable via existing tools.