Skip to main content
Glama

DJs Andorra

Tonight's parties in Andorra

whats_on_tonight
Read-onlyIdempotent

Parties in Andorra tonight (the current night in Andorra time), with venue, DJs and each party's djs.ad link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "whats_on_tonight"
  }
}

Input Schema

NameRequiredDescriptionDefault
djNoA DJ's name or djs.ad slug.
townNoTown or parish, for example "Canillo", "Soldeu" or "Pas de la Casa". Accents and case are ignored.
venueNoA venue's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, so the safety profile is covered. The description usefully defines 'tonight' as the current night in Andorra time, but says nothing about filter combination logic, result ordering, or empty-result behavior.

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?

A single front-loaded sentence with the scope and returned fields; the nested parenthetical is slightly dense but nothing is wasted.

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 three-optional-filter read tool with annotations covering safety and no output schema, the description gives scope, timezone definition and returned fields. Missing only minor operational details such as how the filters combine.

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 schema already documents dj, town and venue, including accent/case handling. The description only confirms these narrow tonight's list and adds the djs.ad link to results, matching the baseline for a fully documented schema.

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?

Names a specific resource and time scope ('Parties in Andorra tonight') and states what comes back (venue, DJs, djs.ad link). The 'tonight' framing implicitly separates it from siblings like this_weekend or search_parties, though no sibling is named.

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 only implied by the 'tonight' scope; there is no explicit statement of when to prefer this over search_parties or this_weekend, and no guidance on combining the optional filters.

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