banca-dati-merito-mcp

Overview Schema Source Related Servers Discussions Admin

Accedi alla Banca Dati

accedi

Idempotent

Opens a Chrome or Edge window on the Banca Dati di Merito login page so users can authenticate with SPID, CIE, CNS or eIDAS, then check the session status.

Instructions

Apre una finestra di Chrome o Edge sulla pagina di accesso della Banca Dati di Merito, dove l'utente entra con SPID, CIE, CNS o eIDAS. Ritorna subito: chiedi all'utente di completare l'accesso nella finestra, poi controlla con stato_sessione. La sessione dura circa due ore.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Oct 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds behavior beyond the annotations: the tool returns immediately rather than waiting for login, the user must manually authenticate via SPID, CIE, CNS, or eIDAS, and the session lasts roughly two hours. These details are essential for correctly sequencing the agent's next action with stato_sessione.

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?

The description is short, front-loaded, and every sentence carries useful operational information: what opens, what the user must do, what the agent should do next, and how long the session lasts.

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

Completeness5/5

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

Given that the tool has no input parameters and no output schema, the description provides enough context to invoke it correctly. It explicitly says the tool returns immediately and directs the agent to verify login via stato_sessione, which is the key missing piece an agent would otherwise need.

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?

There are zero parameters, so there is no parameter ambiguity for the description to resolve. The baseline for a parameterless tool is 4, and no additional parameter guidance is needed.

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?

The description states a specific verb and resource: it opens a Chrome or Edge window on the Banca Dati di Merito login page. It clearly distinguishes this action from the sibling stato_sessione by explaining that this tool starts authentication and that the user must complete login separately.

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?

It gives clear usage context: the user must complete login in the opened window, then the agent should check with stato_sessione. It also notes the session lasts about two hours. It does not explicitly say when not to use it, but the authentication workflow is clear.

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