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

banca-dati-merito-mcp

Cerca valori

cerca_valori
Read-only

Search matching values for a specific field—court office, judge, keyword, or legal reference—to build precise filters; use a name-resolution tool when the target field is unknown.

Instructions

Cerca i valori di un singolo campo che contengono un testo: uffici, giudici, parole chiave o riferimenti normativi (per esempio '1453' trova 'ART. 1453 C.C.'). Per risolvere un nome senza sapere il campo usa risolvi_criteri.

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

Input Schema

NameRequiredDescriptionDefault
areaNoArea della Banca Dati. Le ricerche oggi restituiscono risultati solo in CIVILE; le statistiche contano anche PENALE.CIVILE
campoYes
testoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuine behavioral semantics beyond them: matching is substring/containment based, not exact, as shown by the '1453' inside 'ART. 1453 C.C.' example. It does not mention that results are currently limited to CIVILE, though that constraint lives in the area parameter's schema description.

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, front-loaded with the core purpose, then the disambiguation rule. No filler, and the example is compact and load-bearing.

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

Completeness3/5

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

Adequate for a read-only lookup tool with no output schema: purpose, scope, and alternative are all covered. However, it says nothing about return shape (list of distinct values? ranked? paged?) or about the CIVILE-only result limitation, which materially affects whether a call is useful.

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

Parameters4/5

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

Schema coverage is only 33%, and 'campo' and 'testo' carry no schema descriptions, so the description must compensate—it does, mapping the four enum values to natural-language labels and illustrating the matching behavior for 'testo'. 'area' is left to the schema, which does document it, so the gap is minor rather than critical.

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 ('Cerca') and resource ('valori di un singolo campo che contengono un testo') and enumerates the concrete fields (uffici, giudici, parole chiave, riferimenti normativi). The worked example ('1453' → 'ART. 1453 C.C.') makes the operation unambiguous and distinguishes it from the broader sibling risolvi_criteri.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Per risolvere un nome senza sapere il campo usa risolvi_criteri' names the alternative and the exact condition that selects it. The single-field constraint is also stated up front, which implicitly excludes multi-field resolution.

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