Skip to main content
Glama
Sign In

Vahada — Turkish drink prices

by com.getvahada
OverviewDiscussionsAdmin

Venue prices

venue_prices

Every standing drink price for one venue, plus any happy hours with the days and times they run. Accepts a venue name or its Vahada slug.

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

Input Schema

NameRequiredDescriptionDefault
venueYesVenue name or slug, e.g. 'Fıçı Pera'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It does reveal scope (every standing price, happy hours with days/times) and the accepted identifier, but it does not mention lookup failure, matching behavior, or behavior when a venue has no happy hours.

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 short sentences with no filler. The output scope is front-loaded, followed by input format, and every clause contributes meaningfully.

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 one-parameter tool with no output schema, this is nearly complete: it specifies the result content and input format. It could add error or edge-case behavior, but the low complexity makes that a minor gap.

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

Parameters3/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. The description mostly repeats the schema's name-or-slug input, adding only the 'Vahada' brand detail and the single-venue context, which is marginal additional value.

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 clearly states the resource: every standing drink price for a single venue, plus happy hours with their schedules. It distinguishes scope ('for one venue') from broader price tools, but it does not explicitly name a sibling or use a direct verb, so it stops short of a 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?

The phrasing implies use when you need the full drink price list for a specific venue, and the second sentence states the accepted input. However, it offers no explicit guidance on when to use this versus cheapest_drinks or happy_hours_now, and no exclusions or alternatives are mentioned.

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

All Vahada — Turkish drink prices 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