madda — Moroccan law, article by article

Get previous versions of an article

get_versions

Read-onlyIdempotent

Previous wordings of an article with their validity dates, and the current wording.

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": {
      "lang": "<lang>",
      "slug": "<slug>",
      "key": "<key>"
    },
    "name": "get_versions"
  }
}

Input Schema

Name	Required	Description
`key`	Yes
`lang`	Yes	Language of the text: "ar" (Arabic, most texts) or "fr" (French translation, when published).
`slug`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful behavioral content by disclosing what comes back: prior wordings, their validity dates, and the current wording. It still does not say whether the current wording is a separate field or the newest entry, nor how many versions are returned.

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?

A single economical sentence with the return content front-loaded and no filler. It is efficient, though the terseness borders on under-specification for a three-parameter lookup tool.

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

Completeness3/5

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

With no output schema and no annotations about returns, the description carries the burden of explaining results and does so partially by naming validity dates and the current wording. For a tool requiring three identifiers and returning a multi-version structure, it leaves the shape of the response and the meaning of two parameters unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — just 'lang' is documented in the schema, while 'slug' and 'key' are bare strings with no explanation. The description mentions 'an article' but never clarifies what slug versus key identify or how they relate, so it does not compensate for the coverage gap on two of three required parameters.

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?

The description states a specific resource and scope: prior wordings of an article together with their validity dates, plus the current wording. That is enough for an agent to know this is a version-history retrieval. It stops short of naming how it differs from siblings like get_article or get_text, which likely return only the current text.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says to call this instead of get_article when historical wordings are needed, nor any prerequisite or ordering advice. The agent must infer the selection condition from the phrase 'previous wordings' alone.

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

All madda — Moroccan law, article by article tools Inspect

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

Need Help?