Skip to main content
Glama
Sign In
normativa-andalucia

normativa-andalucia

by ATO097
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

obtener_norma

Retrieve the complete record of an Andalusian regulation by its ID, covering laws, decrees, and resolutions published in the BOJA.

Instructions

Devuelve la ficha completa de una norma a partir de su identificador (campo "id").

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": {
      "id": "<id>"
    },
    "name": "obtener_norma"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond the read-and-return intent. It does not say whether the operation is read-only, what happens when the id does not exist, or whether any permission is needed.

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?

A single front-loaded sentence with no filler; the retrieval action and its key are both stated immediately.

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?

For a one-parameter lookup with an output schema covering return values, the description covers what the tool does and what the input is. Only failure behavior and sibling routing are absent, which are minor for this shape of 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 0%, but the description names the single parameter and ties it to the field "id", giving the agent some semantic anchor. It adds no format guidance (e.g., what an id looks like) beyond the schema's bare string type.

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 and resource: "Devuelve la ficha completa de una norma" and the retrieval key ("a partir de su identificador"). This distinguishes it from contar_normas (counting), buscar_normativa (searching) and leer_texto_boja (reading raw text), though it never names those siblings explicitly.

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 by "a partir de su identificador": you call this when you already have an id. There is no explicit when-to-use vs buscar_normativa, no statement of prerequisites, and no exclusions.

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

Deploy Server

Other Tools