Skip to main content
Glama
Sign In

Storied Collection Venues

by io.github.jchauge
OverviewDiscussionsAdmin

Get venue details

get_venue
Read-only

Get full details for one Storied Collection venue by name. Matching is fuzzy and accent-insensitive ('chateau challain', 'gilmerton', 'Borthwick'). Returns country, year originally built, pricing-from with its currency (never converted), rooms in main house, sleeps, guest house, minimum nights, helipad and EV charging. If no confident match, returns closest suggestions.

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": {
      "name": "<name>"
    },
    "name": "get_venue"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesVenue name or part of it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation: it discloses fuzzy and accent-insensitive matching with concrete examples, states that pricing currency is never converted, enumerates the returned fields, and describes the no-confident-match behavior (closest suggestions). That is exactly the kind of operational context annotations cannot convey.

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?

Four tight sentences, front-loaded with the core action, followed by matching behavior, return contents, and fallback. The parenthetical examples earn their place by clarifying matching semantics; no filler.

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?

There is no output schema, and the description compensates by enumerating the returned fields and the no-match fallback. For a single-parameter read tool with safety already covered by annotations, nothing an agent needs to invoke it correctly is missing.

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 3, but the description adds real meaning: it clarifies that the name match is fuzzy and accent-insensitive and supplies illustrative inputs ('chateau challain', 'gilmerton'), which materially changes how an agent should format the argument.

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 ("Get full details for one Storied Collection venue by name") and explicitly scopes to a single venue, which distinguishes it from sibling search_venues. An agent can identify the correct tool without opening the schema.

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?

The description makes the lookup context clear via "one venue by name" and describes the fuzzy-match fallback, implying when this is appropriate. It stops short of naming search_venues or list_countries as alternatives for exploratory or multi-result needs, so exclusions must be inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Storied Collection Venues toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources