Skip to main content
Glama

Evendo Places

Get details for several venues

get_venues
Read-only

Full details (same fields as get_venue) for up to 50 venues or places in one call, e.g. every stop of an itinerary. Pass ids and/or slugs from previous results; duplicates are fetched once. Results keep the order you passed (ids first, then slugs); anything not found is listed in not_found instead of failing the call.

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

Input Schema

NameRequiredDescriptionDefault
idsNoNode IDs from other tools' results.
slugsNoEvendo slug paths, if you have them instead of IDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description goes further by disclosing deduplication of duplicates, deterministic result ordering, and partial-failure behavior (misses go to not_found instead of failing the whole call) — all non-obvious traits an agent needs. It leaves rate limits and per-entry error shape unstated, so not quite maximal.

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?

Two sentences, front-loaded with the capability and size limit, followed by input sourcing and the ordering/failure guarantees. No filler or restated title text.

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?

Even without an output schema, the description conveys what comes back (same fields as get_venue) and how misses are surfaced (a not_found list), plus ordering. For a two-parameter read tool that is sufficient to call and interpret it correctly.

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 coverage is 100%, so the baseline is met by the schema alone; the description still adds meaning by noting ids and slugs can be combined, that duplicates are collapsed, and that ids are resolved before slugs when ordering results. That ordering rule is genuinely useful semantics not in the schema.

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?

States a specific verb and resource ("Full details ... for up to 50 venues or places in one call") and anchors it to the sibling get_venue by promising identical fields, so the batch-vs-single distinction is unambiguous.

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?

Gives clear invocation context ("e.g. every stop of an itinerary") and a source for inputs ("ids and/or slugs from previous results"), which implicitly routes single-venue lookups to get_venue. It stops short of an explicit when-not or named alternative for the single-item case.

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.