Skip to main content
Glama

Ver la ficha de unas obras

ver_obras
Read-onlyIdempotent

Use this when the user wants to know more about particular buildings: who designed them and when, where they are, what they are like, why they matter, whether they can be visited and what else Builtalist has about them (a story, an audio guide, a competition). Gives the Builtalist entry of up to 5 works, by the id that comes with each work in a search, or by name.

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

Input Schema

NameRequiredDescriptionDefault
idsNoIds of works, as they come in a search: bt-0002f3afcc.
nombresNoNames of works, as precise as possible, with the city if it helps: "Casa da Música, Porto".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint and openWorldHint, so the safety profile is covered. The description adds real context beyond that: the payload is a full record with architect, dates, location, visitability and linked Builtalist content, and the result set is capped at 5. It omits what happens when an id is unknown or when both parameters are supplied.

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?

Two sentences, front-loaded with the usage trigger and a compact enumeration of the record's fields, followed by the return scope and lookup modes. The field list is long but each item maps to real content the agent can surface, so little is wasted; a stricter version would move the lookup mechanics ahead of the field inventory.

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 only two optional parameters, no output schema and annotations covering safety, the description is close to self-sufficient: it explains what the record contains, how many works come back, and how to address them. The remaining gap is edge behavior — no required parameters means nothing states that at least one of ids or nombres must be given.

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% and both parameters carry examples, so the schema does the heavy lifting and the baseline is 3. The description adds the either/or lookup semantics ("by the id ... or by name") and the shared cap of 5, but says nothing about precedence if both are passed or about the partial/loose matching that name lookup presumably involves.

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?

"Gives the Builtalist entry of up to 5 works" states a specific verb (retrieve record) and resource (works/buildings), and the opening clause enumerates what the record contains (architect, dates, location, character, significance, visitability, related content). It implicitly separates itself from search tools by noting ids come "from a search", though it never names a sibling like buscar_obras as the discovery counterpart.

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?

"Use this when the user wants to know more about particular buildings" gives a clear triggering condition, and the id-provenance note ("the id that comes with each work in a search") implies the correct search-then-fetch sequence. It lacks any explicit when-not or exclusion, e.g. that it is unsuitable for open-ended discovery or browsing.

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