Skip to main content
Glama
Sign In

WhatsMood

by com.whatsmood
OverviewDiscussionsAdmin

Compare ticket prices

compare_ticket_prices
Read-onlyIdempotent

Compare ticket prices for one event across official sellers (Biletix, Biletinial, Bubilet and partners): price, currency, category, availability (in_stock, limited, sold_out), cheapest flag and a buy link. Use when the user asks 'how much are tickets', 'cheapest ticket', 'is it sold out'. TR: Bilet fiyatı karşılaştırma.

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

Input Schema

NameRequiredDescriptionDefault
eventIdYesWhatsMood event id from search_events or get_event.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, non-open-world behavior. The description adds useful return semantics: price, currency, category, availability states, cheapest flag, and buy link, which matters because there is no output schema.

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?

The definition is front-loaded: purpose, seller scope, returned fields, then usage triggers. The Turkish line is brief and does not obscure the English guidance.

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 simple one-parameter read tool, it covers purpose, use cases, seller scope, and returned fields, while annotations cover safety. Minor omissions include error behavior if no sellers are found, but nothing essential is missing.

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?

There is only one parameter and schema coverage is 100%, so the schema already explains eventId and where to get it. The description adds only the idea that comparison is for one event, so baseline 3 is appropriate.

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 states a specific verb and resource: comparing ticket prices for one event across named official sellers. It is clearly distinct in substance from event search/detail siblings, though it does not explicitly name an alternative tool.

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?

It gives concrete trigger phrases such as 'how much are tickets', 'cheapest ticket', and 'is it sold out'. It does not state when not to use it or name alternatives like get_event for non-price information.

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

All WhatsMood 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