Skip to main content
Glama
Sign In

WhatsMood

by com.whatsmood
OverviewDiscussionsAdmin

Get event details

get_event
Read-onlyIdempotent

Get details of one WhatsMood event by its numeric id (from search_events or a whatsmood.com/etkinlik/...- URL): title, status, local start time, venue and address, city, coordinates, short description, lowest price, event page URL and calendar (.ics) link. TR: Etkinlik ayrıntısı.

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

Input Schema

NameRequiredDescriptionDefault
eventIdYesWhatsMood event id, e.g. 20099 (the number at the end of the event URL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that by enumerating the response fields (status, local start time, coordinates, lowest price, .ics link), which matters because there is no output schema. It does not say what happens for an invalid or missing id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense, front-loaded sentence carries purpose, id provenance, and return fields with no filler. The trailing Turkish line only restates the title, so it adds little for a non-localizing agent, but it is negligible overhead.

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 single-record lookup with one fully documented parameter and annotations covering safety, the description supplies the two things structured fields do not: id provenance and the shape of the returned data. Only error/failure behavior for a nonexistent id is left unstated.

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% and the schema already explains the integer format and the URL-suffix convention. The description still adds provenance by tying the id to search_events output, giving the agent an upstream workflow rather than just a type.

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?

The description names a specific verb and resource ("Get details of one WhatsMood event") and scopes it to a single record by numeric id, which cleanly separates it from a list/search tool like search_events. It also enumerates the returned fields, so an agent knows exactly what it gets back.

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 tells the agent where the required id comes from (search_events results or a whatsmood.com/etkinlik/...-<id> URL), which is the practical precondition for calling it. It stops short of an explicit when-not-to-use statement or a direct comparison to siblings such as compare_ticket_prices.

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