Skip to main content
Glama

Obtener norma por idNorma o número

obtener_norma

Fetch metadata of a Chilean legal norm by ID, number, or search query, with results in markdown or JSON format.

Instructions

Metadatos BCN de una norma chilena.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numeroNo
formatoNoFormato de salida: markdown (recomendado para citas) o jsonmarkdown
consultaNo
id_normaNo
Behavior2/5

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

No annotations provided; the description only indicates a read operation (metadatos) but lacks details on output structure, side effects, or authentication requirements. Minimal disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it omits essential details making it minimally adequate.

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

Completeness1/5

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

Given 4 parameters with no output schema and no annotations, the description is severely incomplete. It does not explain usage, output, or how it complements sibling tools.

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

Parameters1/5

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

Description provides no information about any of the 4 parameters. With schema coverage at 25%, the description fails to clarify how parameters like id_norma, numero, consulta are used.

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

Purpose3/5

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

The description states it retrieves metadata of a Chilean norm, but does not mention the search criteria (idNorma or number) or differentiate from sibling tools like obtener_texto_norma or obtener_articulo.

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?

No guidance on when to use this tool versus alternatives such as buscar_legislacion or obtener_texto_norma. No mention of prerequisites or context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gabrielperezibacache/mcp-legal-chile'

If you have feedback or need assistance with the MCP directory API, please join our Discord server