Skip to main content
Glama

Buscar exposiciones en Madrid

buscar_exposiciones
Read-onlyIdempotent

Use this when the user asks what exhibitions are on in Madrid (architecture, design, photography, art), today or on some dates. Lists the ones Builtalist follows that are open on those days, each with its type, venue, dates, price and link. For now, only Madrid.

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

Input Schema

NameRequiredDescriptionDefault
desdeNoYYYY-MM-DD. Today if not given.
hastaNoYYYY-MM-DD. The same day as "desde" if not given.
textoNoWords in the title, the type (arquitectura, fotografía, diseño), the artists or the venue.
limiteNoHow many works to give, from 1 to 20. 10 if not given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond that: only exhibitions followed by Builtalist are returned, they must be open on the requested days, and each result includes type, venue, dates, price, and link. It does not describe sorting or pagination, preventing a 5.

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?

The definition is two tight sentences plus a short scope note, front-loaded with the usage trigger. Every sentence earns its place by covering trigger, source, return contents, and geographic scope.

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 no output schema, the description helpfully lists the fields each result contains and names the data source. It is nearly complete for a simple read-only search tool; the only missing details are minor, such as sorting order or whether past exhibitions are ever included.

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 the schema already explains desde, hasta, texto, and limite, including defaults and limits. The description only weakly echoes these through 'today or on some dates' and the list of exhibition types, adding little meaning beyond the structured fields.

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 states a specific verb and resource ('asks what exhibitions are on in Madrid') and scopes the domain explicitly (architecture, design, photography, art). It is easy to distinguish from siblings such as buscar_concursos or buscar_obras, which cover different content types.

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 gives a clear trigger ('Use this when the user asks what exhibitions are on in Madrid'), mentions date-based queries, and adds a scope constraint ('For now, only Madrid'). It does not name a competing tool or an explicit when-not condition, but no sibling appears to overlap in domain, so the remaining gap is minor.

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