Skip to main content
Glama

Who is playing tonight

whos_playing
Read-onlyIdempotent

Lists the announced DJ nights in one djbnb city tonight or this weekend: time, night, venue, door price when known, and the DJs on the bill, each with its djbnb link. Start times are local to the city.

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

Input Schema

NameRequiredDescriptionDefault
cityYesA city name such as Detroit or Salt Lake City, or a slug from list_cities such as detroit-mi.
whenNotonight (the default) or this_weekend (Friday to Sunday).

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?

Annotations already cover read-only, idempotent, non-destructive behavior, so the description only needs to add context — and it does: it discloses the returned fields, that door price may be absent ('when known'), and that start times are city-local. It stops short of noting result limits or empty-result behavior, but the added detail is genuinely useful.

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, front-loaded with the verb and scope, followed by the return shape and one caveat. No filler or restated title.

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?

With only two well-documented parameters and no output schema, the description supplies enough: what is listed, what comes back, that price is conditional, and that times are local. Minor gaps (result count, behavior when nothing is scheduled) are not blocking for a read-only listing tool.

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 both parameters, including the when enum and city slug format, are already documented. The description's 'tonight or this weekend' mirrors the enum without adding new meaning, and 'one city' only weakly reinforces the single-city constraint. Baseline 3 applies since the schema carries the load.

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 (lists), a specific resource (announced DJ nights), and the exact scope (one djbnb city, tonight or this weekend), then enumerates the returned fields. An agent can tell immediately this is a city-scoped event listing rather than a city catalog like list_cities.

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?

Usage is implied by the scope ('in one djbnb city tonight or this weekend') but there is no explicit statement of when to prefer this over siblings or what to do if the city is unknown. The schema hints at list_cities for slugs, but the description itself offers no routing or prerequisites.

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.

Resources