Skip to main content
Glama

Cerca itinerari

search_day_plans
Read-onlyIdempotent

Find available day plans around coordinates for a date and audience. Returns ids for get_day_plan. Does not create a new itinerary. Results include source attribution and public DalVivo URLs.

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": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "search_day_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lngYes
dateNo
limitNo
cursorNo
audienceNo
radius_mNo

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, closed-world behavior, so the safety profile is covered. The description adds real value beyond that: it says what comes back (ids for get_day_plan, source attribution, public DalVivo URLs) and confirms no itinerary is created. It omits pagination and limit behavior even though a cursor parameter exists.

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?

Four short sentences, front-loaded with the core purpose and the follow-up tool reference. The negation sentence earns its place as disambiguation, though the trailing return-shape sentence could be tightened.

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, describing the return payload is genuinely useful, and the description does some of that. But a 7-parameter search tool with 0% schema coverage needs radius, limit, and cursor semantics explained, and none are present.

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%, so the description carries the full burden, and it only glosses lat/lng/date/audience without format or constraint detail. radius_m (in meters, default 30 km), limit (default 5, max 10), and cursor (pagination) get no mention at all, which are the params most likely to be misused.

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?

"Find available day plans around coordinates for a date and audience" gives a specific verb plus resource and scope, and "Returns ids for get_day_plan" separates it from the detail-fetch sibling. It does not explicitly contrast with search_events/search_places, but the resource noun (day plans) is distinct enough that an agent can route correctly.

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?

The description implies a two-step workflow (search here, then get_day_plan with the returned ids) and rules out creation with "Does not create a new itinerary." It never states when to prefer this over the sibling search_events or search_places tools, so guidance is implied rather than explicit.

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