Skip to main content
Glama

Citar texto legal oficial con blockquote

citar_texto_legal

Generate formal Chilean legal citations with official text from LeyChile, ready to paste into legal documents.

Instructions

Devuelve cita formal chilena + texto oficial de LeyChile listo para pegar en un escrito (blockquote).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
letraNo
incisoNo
formatoNoFormato de salida: markdown (recomendado para citas) o jsonmarkdown
articuloYes
id_normaYes
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the output (citation + text blockquote) but omits any side effects, authentication requirements, rate limits, or external dependencies. The tool likely fetches data from LeyChile, but this is not disclosed.

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 very concise (one sentence) and front-loaded with the main purpose. However, it is too brief to convey necessary details, making it merely adequate rather than efficiently informative.

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

Completeness2/5

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

Given the 5 parameters, 2 required, no output schema, and no annotations, the description is incomplete. It does not explain return format details (beyond 'blockquote'), provide usage examples, or clarify what constitutes a 'cita formal chilena'.

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 20% (only 'formato' has a description). The description does not explain the meaning of 'id_norma', 'articulo', 'letra', or 'inciso' beyond what the schema provides. For a low-coverage schema, the description should compensate but does not.

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 clearly states the tool returns a formal Chilean citation plus official text in blockquote format, using specific verbs and resources. However, it does not differentiate from sibling tools like 'obtener_articulo' or 'formatear_cita', which may have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives. No context about prerequisites, limitations, or exclusions is given.

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