Skip to main content
Glama

get_bando_details

Restituisce la scheda tecnica completa e raffinata di un singolo bando (Clean Fuel per LLM).

Args:
    uuid: Identificativo del bando (es. 'mimit-transizione-5-0', 'lombardia-voucher-digitalizzazione-2026')

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": {
      "uuid": "<uuid>"
    },
    "name": "get_bando_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Restituisce' implies a read-only retrieval, but the description does not state error behavior, permissions, rate limits, or what happens when the uuid is unknown.

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?

The purpose is front-loaded in a single clear sentence, followed by a compact Args block for the only parameter. The parenthetical '(Clean Fuel per LLM)' is somewhat unclear, but overall the description is efficient and appropriately sized.

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?

This is a simple one-parameter retrieval tool, and an output schema already exists, so the description need not explain return values. The main missing context is how to obtain the uuid and any failure behavior, but for a straightforward detail lookup it is largely complete.

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 description coverage is 0%, but the description compensates well by explaining that uuid identifies the bando and providing concrete examples such as 'mimit-transizione-5-0'. It does not specify format constraints or where the uuid should come from, keeping it short of complete compensation.

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?

The description clearly states the verb and resource: it returns the complete technical sheet of a single bando. It distinguishes a single-bando lookup from list/search behavior implicitly, but does not explicitly name search_bandi as the sibling used to find a uuid.

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?

Usage is implied by 'singolo bando' and the required uuid parameter, so an agent can infer this is for fetching details when the identifier is already known. However, there is no explicit guidance on when to use this versus search_bandi or how to obtain the uuid.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources