Skip to main content
Glama

Map a clause across frameworks

map_clause
Read-onlyIdempotent

Map one clause of a framework to the others through the topic crosswalk (25 governance topics against the EU AI Act, GPAI Code, GDPR, ISO/IEC 42001 and related standards, NIST AI RMF, CSA AICM, OWASP, Korea, UK, Singapore, Council of Europe, OECD, G7, CEN-CENELEC and the Chinese instruments). Give the framework ("EU AI Act", "iso-42001", "NIST AI RMF", "GDPR") and the clause as the framework writes it ("Art. 9", "Article 10(2)", "6.1.2", "GOVERN 1", "A.6", "LLM01"). Returns each topic the clause sits in, with the clauses of the other frameworks on that topic, their strength (core or related) and the obligation-register ids joined to them.

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": {
      "framework": "<framework>",
      "ref": "<ref>"
    },
    "name": "map_clause"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesClause reference, e.g. "Art. 9", "6.1.2", "GOVERN 1".
frameworkYesFramework id or name.

Output Schema

NameRequiredDescriptionDefault
refYes
viaYesWhere the clause was found.
noticeYesIllustrative, not legal advice and not a claim of conformity.
sourceYesCanonical URL of the page this answer comes from; cite it.
datasetYesURL of the open-data document the answer was read from.
licenseYesLicence of the data (CC BY 4.0, attribution required).
matchesYes
frameworkYes
dataVersionYesBody of Knowledge version of the data.
frameworkIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is explaining the mechanism (topic crosswalk) and the result shape: topics, other frameworks' clauses, core-vs-related strength, and joined obligation-register ids. It does not mention limits such as behavior for an unmapped clause reference, which keeps it from a 5.

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?

Purpose is front-loaded in the first clause and the rest supports it. The long parenthetical inventory of standards bodies is informative but runs on and could be trimmed without losing calling guidance.

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 two-parameter read tool with an output schema, the definition covers inputs, the mapping mechanism, scope of the crosswalk, and the shape of results. Nothing an agent needs in order to call it correctly is missing.

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% with per-parameter descriptions, so baseline would be 3, but the description goes beyond by listing accepted framework spellings (including lowercase ids like 'iso-42001') despite no enum, and by enumerating clause-format variants ('Art. 9', 'Article 10(2)', '6.1.2', 'GOVERN 1', 'A.6', 'LLM01'). That materially reduces guesswork on the unconstrained string inputs.

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?

States a specific verb and resource ('Map one clause of a framework to the others through the topic crosswalk') and goes further by naming the covered frameworks and the 25-topic crosswalk scope. An agent can tell this apart from lookup siblings like get_control or get_obligation, which retrieve a single artifact rather than relate clauses across frameworks.

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

Usage Guidelines4/5

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

Gives clear invocation context: supply the framework name and the clause exactly as that framework writes it, with concrete format examples. It does not state explicit exclusions or name a sibling to use when you only want one framework's text, so it stops short of full when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.