Skip to main content
Glama

DJs Andorra

Search coming parties in Andorra

search_parties
Read-onlyIdempotent

Coming parties in Andorra, filtered by night range, town, DJ, venue or free text. Soonest first.

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

Input Schema

NameRequiredDescriptionDefault
qNoFree text matched against party name, venue, town and DJs.
djNoA DJ's name or djs.ad slug.
toNoLast night to include, YYYY-MM-DD.
fromNoFirst night to include, YYYY-MM-DD (Andorra nights).
townNoTown or parish, for example "Canillo", "Soldeu" or "Pas de la Casa". Accents and case are ignored.
limitNoAt most this many (default 20).
venueNoA venue's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world behavior, so the bar is lower. The description nonetheless adds two genuinely useful traits beyond the annotations: results are limited to upcoming ('coming') parties and are ordered soonest-first, which affects how an agent interprets the result list.

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 short sentences with no filler; the resource and scope come first, followed by the filters and the sort order. Every clause carries information an agent can use.

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 seven-parameter, all-optional search with full schema coverage and read-only annotations, the definition covers scope, filters, and ordering adequately. It stops short of stating whether the date range is bounded or how results are shaped, but no output schema exists and the omission is minor for a simple list 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 description coverage is 100%, so every parameter is already documented, including date format, town accent-insensitivity, and the default of 20 with a max of 50. The description merely re-lists the filter dimensions (night range, town, DJ, venue, free text) without adding syntax or precedence rules, so the 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 states a concrete resource and scope: 'Coming parties in Andorra', filtered by night range, town, DJ, venue, or free text, returned soonest-first. That is enough for an agent to know it is a faceted list/search over upcoming events, though it never names or contrasts itself with the time-scoped siblings (this_weekend, whats_on_tonight).

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 enumeration of filter facets and the 'Soonest first' ordering; there is no explicit statement of when to prefer this over this_weekend or whats_on_tonight, nor when a single-party lookup (get_party) is the right call. An agent can infer a general search, but must guess at the boundaries with siblings.

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