Skip to main content
Glama

Cerca eventi

search_events
Read-onlyIdempotent

Find events by date, coordinates, keywords, free admission and family suitability. Geographic filters require both coordinates. Maximum 10 results per page. Results include source attribution and public DalVivo URLs.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
ageNo
latNo
lngNo
sortNoupcoming
limitNo
cursorNo
date_toNo
languageNo
radius_mNo
date_fromNo
free_onlyNo
family_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description adds genuine behavioral content beyond them: the coordinate-pairing prerequisite, the pagination ceiling of 10 results per page, and the fact that results carry source attribution and public DalVivo URLs. It stops short of explaining cursor semantics or result ordering.

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?

Three tight sentences, front-loaded with capability before constraints and return shape, with no filler. The minor redundancy is 'Maximum 10 results per page,' which largely restates the schema's limit maximum of 10.

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?

With no output schema, the note about source attribution and DalVivo URLs usefully covers return content, and the coordinate rule covers the most common misuse. But for a 13-parameter search tool with zero schema descriptions, the silence on sort, cursor, radius_m, age and language leaves real gaps an agent would have to resolve by trial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 13 parameters, so the description carries the full explanatory burden and only partly delivers. It loosely maps to q, date_from/date_to, lat/lng, free_only and family_only, but says nothing about sort values, limit, the cursor-based pagination mechanism, radius_m, age, or language, all of which the agent must guess at.

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 opens with a concrete verb and resource ('Find events') and enumerates the filter dimensions: date, coordinates, keywords, free admission, family suitability. It never contrasts itself with siblings such as search_places or search_day_plans, so an agent must infer the domain split, which keeps it at 4 rather than 5.

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?

Use is implied by the filter list, and one real constraint is stated ('Geographic filters require both coordinates'), which tells the agent not to send lat or lng alone. There is no explicit when-to-use guidance, no statement that get_event should be used for a known ID, and no indication of what to do when no filters match.

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