Skip to main content
Glama

A2A Defense & Monetization Gateway

verify_normative_validity

Verificación determinista en grafo legal de vigencia, modificación o derogación de artículos normativos (Código Tributario, Civil, LPAG).

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": {
      "codigo_norma": "<codigo_norma>",
      "articulo": "<articulo>"
    },
    "name": "verify_normative_validity"
  }
}

Input Schema

NameRequiredDescriptionDefault
articuloYesNúmero de artículo a verificar (ej. 43, 44, 1989, 207)
fecha_corteNoFecha de corte opcional (YYYY-MM-DD)
codigo_normaYesCódigo de la norma (ej. CODIGO_TRIBUTARIO, CODIGO_CIVIL, LEY_27444)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It does disclose a meaningful trait by calling the verification 'determinista' and graph-based, which tells the agent results are reproducible lookups rather than model judgments, and it names the three outcomes tracked (vigencia, modificación, derogación). It omits read-only guarantees, permission/auth needs, and what the response looks like.

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 core verb and scope come first and the parenthetical code list is compact and useful. Nothing in it is redundant.

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 3-parameter, non-destructive verification tool with a fully described schema and no output schema, the definition covers purpose, domain, and the deterministic nature of the check. The main residual gap is the shape of the verdict returned and how fecha_corte selects a version of the legal graph, but the essentials for correct invocation are present.

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 coverage is 100%, so all three parameters are already documented in the schema, which sets the baseline at 3. The description marginally reinforces semantics by naming which codes codigo_norma accepts and tying 'artículo' to normative articles, but adds no format or behavior detail for fecha_corte beyond what the schema already says.

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 gives a specific verb ('Verificación determinista') and resource ('grafo legal de vigencia, modificación o derogación de artículos normativos'), and scopes it to named codes (Código Tributario, Civil, LPAG). An agent can tell it checks legal validity of an article rather than doing something else. It stops short of differentiating itself from siblings by name, but the domain is distinctive enough.

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?

There is no explicit when-to-use or when-not guidance, no mention of prerequisites, and no reference to alternatives. The agent can infer usage from the phrase 'artículos normativos' and the enumerated codes, but nothing states the decision context, e.g. when to trust this deterministic check versus a general lookup.

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.

Resources