cl-eli-mcp

cl_get_norm

Read-onlyIdempotent

Retrieve complete metadata for a Chilean law, decree, or resolution by supplying its BCN resource URI. Get all available details for that single norm.

Instructions

Fetch full detail for one Chilean norm by its BCN resource URI.

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": {
      "uri": "<uri>"
    },
    "name": "cl_get_norm"
  }
}

Input Schema

Name	Required	Description	Default
`uri`	Yes	e.g. ``"http://datos.bcn.cl/recurso/cl/ley/ministerio-de-justicia/1984-02-07/18290"``.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, etc. The description adds 'Fetch full detail' which is consistent but does not provide additional behavioral information such as error handling, rate limits, or authentication needs. With annotations covering the safety profile, the description adds minimal extra transparency.

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?

The description is a single, concise sentence that immediately conveys the tool's purpose. It is front-loaded with the key action and resource, with no wasted words.

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 one parameter, clear annotations, and an output schema (as indicated by context), the description is adequate. It could be enhanced by noting the output schema covers the full detail, but it is not necessary. The description is complete for this simple tool.

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%, so the schema already documents the parameter. The tool description mentions 'by its BCN resource URI' which mirrors the schema's description. No new semantic information is added beyond what the schema provides. Baseline of 3 is appropriate.

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?

Description clearly states it fetches full detail of one Chilean norm by its BCN resource URI. The verb is specific, and the distinction from sibling tool 'cl_search_norms' is implied by focusing on a single norm by URI rather than searching.

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: use this when you have a specific URI. However, no explicit guidance is given about when not to use it or when to prefer the sibling tool 'cl_search_norms'. The description lacks explicit when/when-not alternatives.

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

Deploy Server