Skip to main content
Glama

Buscar concursos de arquitectura

buscar_concursos
Read-onlyIdempotent

Use this when the user asks about an architecture competition: who won, who else took part, what was proposed for a building or a place, or which competitions there were in a city or a period. Lists the competitions in Builtalist, each with its year, building, number of entries and winner, and a link to see the winning entry next to the others.

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_concursos"
  }
}

Input Schema

NameRequiredDescriptionDefault
desdeNoHeld in this year or later.
hastaNoHeld in this year or earlier.
textoNoA building, a place, a city or an architect: "Prado", "Helsinki", "Nouvel".
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?

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value by disclosing the return contents (year, building, number of entries, winner, link to compare entries) and the closed corpus ('in Builtalist'), which the annotations alone do not convey.

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: the first front-loads the triggering conditions, the second the result shape. No filler, no repetition of the title, and each sentence carries distinct information.

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 simple read-only search with four optional parameters and no output schema, the definition is nearly complete: it explains triggers and describes the returned fields. It omits ordering and what happens when limite truncates results, but that is a minor gap for this tool's complexity.

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%, with desde/hasta, texto and limite each documented, so the baseline is 3. The description reinforces that texto covers buildings, places, cities and architects and that the year range bounds when a competition was held, but it adds no syntax or behavior beyond what the schema already says.

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 ("Lists the competitions in Builtalist") and enumerates the question shapes it answers: who won, who else took part, what was proposed, and which competitions existed in a city or period. Against siblings like buscar_exposiciones, buscar_obras and buscar_historias, the 'architecture competition' resource is unambiguous.

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?

The opening clause gives explicit when-to-use guidance with concrete user-question examples, which is stronger than most definitions. It does not state when not to use it or point to a sibling for the adjacent cases (works, exhibitions), so it stops short of full routing guidance.

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