Skip to main content
Glama
banca-dati-merito-mcp

banca-dati-merito-mcp

Risolvi criteri di ricerca

risolvi_criteri
Read-only

Converts a user-supplied court, city, judge, or subject into the exact Banca Dati search criteria and field needed before searching, ensuring filters match valid values.

Instructions

Trasforma un nome detto dall'utente (un tribunale, una città, un giudice, un tema) nei criteri esatti della Banca Dati, con il campo giusto. Usalo prima di cercare per ufficio, distretto, giudice, parola chiave o materia: i criteri funzionano solo con il valore esatto.

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": {
      "testo": "<testo>"
    },
    "name": "risolvi_criteri"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoArea della Banca Dati. Le ricerche oggi restituiscono risultati solo in CIVILE; le statistiche contano anche PENALE.CIVILE
tipoNoprovvedimenti (sentenze, ordinanze, decreti) oppure abstract (sintesi dei principi).provvedimenti
testoYesIl nome o il tema, come lo dice l'utente.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description meaningfully adds the key behavioral constraint — that downstream search only accepts the exact value returned — which an agent would not infer from the schema. It does not say what happens when a name cannot be resolved (no match, ambiguity), which keeps it below 5.

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?

Two sentences, zero waste, with the purpose front-loaded and the usage rule immediately after. Every clause carries information.

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?

Complete on intent, usage and the exact-value constraint, and there is no output schema to explain. However, since no output schema exists, the description could have said what form the resolved criteria take (field/value pairs) so the agent knows how to feed them downstream. That is the only remaining gap.

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 explains area (CIVILE-only results, PENALE for statistics), tipo enum, and testo. The description adds that 'testo' is the raw user-spoken name, but nothing beyond the schema about area/tipo. Baseline 3 applies.

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?

States a specific verb+resource: it transforms a user-spoken name (court, city, judge, topic) into exact Banca Dati criteria with the correct field. This clearly separates it from the search siblings (cerca_provvedimenti, cerca_valori) by framing it as a pre-search resolver.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Usalo prima di cercare per ufficio, distretto, giudice, parola chiave o materia" gives explicit ordering and target cases, plus the rationale that criteria only work with exact values. It lacks an explicit "when not to use" or a named alternative such as elenca_valori/cerca_valori for browsing, so it falls short of a 5.

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