madda — Moroccan law, article by article

Get an article

get_article

Read-onlyIdempotent

One article of a text, exactly as published, with its citation block (canonical URL, marker, text title and number, consolidated date, official PDF).

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_article"
  }
}

Input Schema

Name	Required	Description
`key`	Yes	Article key, e.g. 4, 5-bis, 185-to-200
`lang`	Yes	Language of the text: "ar" (Arabic, most texts) or "fr" (French translation, when published).
`slug`	Yes	Text slug, e.g. loi-70-03

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that content is verbatim as published and enumerates the citation-block fields it returns. It stays silent on failure behavior, notably that requesting lang='fr' can yield nothing when no French translation is published.

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 compact sentence with the core resource front-loaded and the returned citation components appended. Slightly compressed as a noun fragment ('One article of a text'), but nothing is wasted.

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?

With only three fully documented required parameters and no output schema, the description does the necessary work of describing what comes back (body text plus canonical URL, marker, title, number, date, PDF). Coverage is adequate; only error and empty-result behavior is missing.

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%, with examples for key ('4, 5-bis, 185-to-200'), slug ('loi-70-03') and the lang enum, so the schema already carries the parameter semantics. The description adds no further meaning about these parameters, which is acceptable at full coverage.

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 pairing (fetch one article of a text) and specifies fidelity ('exactly as published') plus the returned citation block. It does not differentiate itself from the sibling get_text, so an agent must infer that get_text returns the whole text while this returns one article.

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 explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as get_text or search_law. The only implied guidance is that callers already know a lang/slug/key triple, which is not enough to route between siblings reliably.

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?