Skip to main content
Glama

Evendo Places

Get venue details

get_venue
Read-only

Full details for one venue or place: description, address, coordinates, phone, website, booking link, photos, and all attribute tags. Pass the id from a previous result (or a slug like 'united-kingdom/london'). For several venues at once, use get_venues.

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

Input Schema

NameRequiredDescriptionDefault
idNoNode ID from another tool's results.
slugNoEvendo slug path, if you have it instead of an ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description earns credit by disclosing the shape of the return payload, which matters since there is no output schema. It does not say what happens when neither id nor slug is supplied, or how a not-found id is reported, which is the remaining gap for a zero-required-parameter lookup.

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, no redundancy: the return-field inventory comes first so the agent can judge relevance, then the parameter guidance and the sibling hand-off. The long field list is informative content rather than padding.

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?

For a read-only, two-optional-parameter lookup with no output schema, the description covers both what it returns and how to address the record, which is the bulk of what an agent needs. The only omission is the edge case of supplying neither identifier.

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 baseline is 3, but the description adds a concrete slug format example ('united-kingdom/london') that the schema only gestures at with 'Evendo slug path'. The 'or' construction also signals the id/slug are interchangeable selectors rather than complementary inputs.

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?

Specific verb+resource ('Full details for one venue or place') followed by an enumerated field list (address, coordinates, phone, website, booking link, photos, tags) that tells an agent exactly what comes back. It explicitly contrasts with get_venues for batches, so the sibling boundary is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the invocation precondition ('Pass the id from a previous result') plus an accepted alternative ('or a slug like united-kingdom/london'), and names the alternative tool with its selecting condition ('For several venues at once, use get_venues'). Nothing about when to choose this vs. the bulk variant is left to inference.

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.