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

banca-dati-merito-mcp

Ricerche salvate

ricerche_salvate
Read-only

Retrieves the searches you have saved in the Banca Dati di Merito, read-only. Use it to list saved searches for decisions or abstracts and revisit prior search criteria.

Instructions

Elenca le ricerche che l'utente ha salvato nella Banca Dati (sola lettura).

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": "ricerche_salvate"
  }
}

Input Schema

NameRequiredDescriptionDefault
tipoNoprovvedimenti (sentenze, ordinanze, decreti) oppure abstract (sintesi dei principi).provvedimenti

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior2/5

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

The parenthetical "(sola lettura)" merely restates readOnlyHint=true from the annotations, adding no new information. Nothing is said about pagination, result limits, what a saved search record contains, or the openWorldHint implication that results may include external/unknown entries.

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?

One short sentence with the resource front-loaded and zero filler. It is efficient, though the terseness is part of why other dimensions are thin.

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?

For a single-optional-parameter read tool with annotations covering safety and a fully documented schema, the essential information is present. Still missing is whether the tool requires an authenticated session and how many saved searches are returned, which matters given the openWorld annotation.

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 the single enum parameter 'tipo' is fully documented in the schema, including both values and their meanings. The description adds nothing about it, so the baseline 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?

Clear verb+resource: "Elenca le ricerche che l'utente ha salvato nella Banca Dati", telling the agent this returns a list of saved searches rather than documents. It does not, however, distinguish itself from plausible siblings such as cartelle_personali or archivio, which an agent could easily confuse with saved-search listings.

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 statement of when to use this tool, what prerequisites exist (e.g. being logged in via accedi), or which sibling to prefer when the user wants folders or documents instead of saved searches. Usage is only inferable from the name and the resource noun.

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