Skip to main content
Glama

search_bandi

Cerca bandi e agevolazioni pubbliche attive in Italia per parola chiave, regione o tipologia.

Args:
    query: Testo da cercare (es. 'digitalizzazione', 'transizione ecologica', 'software')
    regione: Filtro geografico (es. 'Lombardia', 'Lazio', 'Emilia-Romagna', 'Nazionale')
    tipo_agevolazione: Filtro tipo (es. 'Fondo Perduto', 'Credito Imposta')
    status: Stato bando ('Aperto', 'In Arrivo', 'Chiuso')

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

Input Schema

NameRequiredDescriptionDefault
queryNo
statusNoAperto
regioneNo
tipo_agevolazioneNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 and mostly leaves it unaddressed. It does not say whether the search is full-text or exact, how results are ordered or capped, whether pagination exists, or whether a null query returns everything — all relevant for a discovery tool. It also contains a mild tension: it advertises only 'active' grants while the status parameter accepts 'Chiuso'.

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 sentence is front-loaded in a single line, followed by a compact Args block — no filler prose. Minor redundancy in restating parameter names already present as schema titles, but each line adds an example, so it earns its place.

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?

An output schema exists, so return-value explanation is correctly omitted. However, for a four-filter search tool with no annotations, the description says nothing about result volume, ranking, or whether criteria combine with AND or OR — gaps an agent would want to know before calling.

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% (only titles), so the description must compensate, and it does: every one of the four parameters gets both a meaning and concrete example values. It notably enumerates the valid status values ('Aperto', 'In Arrivo', 'Chiuso') that the schema does not declare as an enum, which is real added value.

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?

States a specific verb+resource combination ('Cerca bandi e agevolazioni pubbliche attive in Italia') plus the three filter axes, which is far more informative than the bare name. It does not, however, distinguish itself from the sibling get_bando_details, so an agent must infer that this tool returns a list while that one returns a single record.

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 the word 'attive' and by the default status of 'Aperto', giving some sense of the intended default scope. There is no explicit statement of when to prefer this over get_bando_details or the CORDIS search siblings, and no note that all parameters are optional, so the agent must infer the workflow.

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