Skip to main content
Glama

DJs Andorra

Parties this weekend in Andorra

this_weekend
Read-onlyIdempotent

Parties from Friday to Sunday: this weekend, or the next one when asked from Monday to Thursday.

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

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.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), so the bar is lower, and the description still contributes the genuinely non-obvious detail of how the weekend window is resolved relative to the current weekday. It doesn't say what happens when no parties match or what the response shape looks like.

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 that leads with the resource and window, then qualifies the edge case. Nothing is redundant, though the phrasing reads as a fragment rather than a fully formed statement of purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with three optional filters and no output schema, the description covers the core temporal semantics adequately. It omits result behavior (empty results, ordering, whether filters are conjunctive), which an agent would need to call it confidently.

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 description coverage is 100%, so dj, town, and venue are already documented in the schema with examples and accent/case handling. The description adds nothing about how these filters combine or whether they are ANDed, so baseline 3 applies.

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 names the resource (parties) and the scope (Friday to Sunday), and adds a non-obvious resolution rule for which weekend counts. It doesn't explicitly contrast itself with 'whats_on_tonight' or 'search_parties', so an agent must infer the temporal split from the sibling names alone.

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?

'this weekend, or the next one when asked from Monday to Thursday' gives a concrete rule for interpreting the request, which is real usage guidance. There is no explicit when-not or alternative routing, so an agent comparing this against 'whats_on_tonight' gets no stated selection criteria.

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