Skip to main content
Glama
Sign In
qavanin-mcp

qavanin-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Amendments of a law

qv_amendments
Read-onlyIdempotent

Trace which laws amended a given law, which laws it amends, and which of its articles were amended. Use it to map amendment relationships before checking full article history.

Instructions

Which laws amended this one, which this one amends, and which of its articles were amended.

Returns amended_by, amends and articles (section id, label, changes, latest). Full history: qv_article_history.

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": {
      "ids": "<ids>"
    },
    "name": "qv_amendments"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesId from qv_search, e.g. '12021850837713548188'.
limitNoMax laws per direction.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.1
    • changedInput schema / properties / ids / description
      Previous value: -"Law id (IDS) from qv_search, digits only, e.g. '12021850837713548188'."New value: +"Id from qv_search, e.g. '12021850837713548188'."
    • changedInput schema / properties / limit / description
      Previous value: -"Max amending/amended laws listed per direction."New value: +"Max laws per direction."
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing the return keys (amended_by, amends, articles with section id, label, changes, latest), which matters because no output schema exists, but it says nothing about pagination or ordering behavior.

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 compact lines: purpose, return shape, cross-reference. The purpose is front-loaded and no sentence is filler.

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?

For a two-parameter read tool with no output schema, the description covers what it returns and where to go for history. Only pagination/ordering of the limit-capped results is unaddressed.

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 description coverage is 100% and the schema already explains the id format (from qv_search) and that limit caps laws per direction. The description adds no syntax, default, or edge-case meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: it returns which laws amended this one, which it amends, and which of its articles were amended. It also routes the agent elsewhere for 'Full history: qv_article_history', giving partial sibling differentiation, though it doesn't contrast with qv_related or qv_law_info.

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

Usage Guidelines3/5

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

Usage is implied by the return keys and by the pointer to qv_article_history for full history. There is no explicit statement of when to prefer this over qv_related or qv_law, and no prerequisites are given.

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

Deploy Server

Other Tools