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

banca-dati-merito-mcp

Frequenza delle parole chiave

frequenze_parole_chiave
Read-only

Identify frequently used keywords in Italian civil decisions or abstracts, with document counts, to reveal common legal themes.

Instructions

Restituisce le parole chiave più usate nei provvedimenti o negli abstract, con il numero di documenti.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "frequenze_parole_chiave"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior3/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 adds that results are paired with document counts, which is useful behavioral content, but it omits how many keywords are returned, how they're ordered, whether a limit exists, and the schema's important caveat that statistics include PENALE while searches do not.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the resource and the returned value come first. It is efficient, though so short that it leaves obvious questions unanswered.

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?

There is no output schema and no required parameters, so the description is the only place a caller could learn the shape, size, or ordering of the keyword list — and it says nothing about those. Adequate for a simple read tool, but it leaves the return contract partially undefined.

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% and both parameters carry their own descriptions with an enum and a default, so the schema does the work. The description adds no meaning about area/tipo beyond restating that both domains exist, so the baseline of 3 applies.

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?

"Restituisce le parole chiave più usate nei provvedimenti o negli abstract, con il numero di documenti" names a specific operation (frequency aggregation) over a specific resource, which distinguishes it from the cerca_*/leggi_* siblings. It just doesn't explicitly name any sibling to contrast with.

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?

The verb "più usate" plus "numero di documenti" implies statistical/aggregate usage rather than document retrieval, so the intended use case is inferable. But the description never says when to prefer this over cerca_provvedimenti or elenca_valori, and gives no exclusions or prerequisites.

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