Skip to main content
Glama

HammerMap: Spanish court, State and Social Security auctions

Get one listing

get_listing
Read-onlyIdempotent

Full record for one listing by id from search_listings (SUB-… for court auctions, BOE-B-… for State sales from the BOE, TGSS-… for Social Security (TGSS) auctions): lots with starting price and deposit, bid deadline, auction session date, bidding mode, approximate place, HammerMap's general risk analysis with legal basis (not legal advice), corrections, official BOE and portal links, and data freshness (attribution.data_updated). Returns an error if the id is not listed any more. Bids and payments happen only on the official channel in urls / bidding.where.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesListing id exactly as returned by search_listings, e.g. SUB-JA-2026-267510 or BOE-B-2026-35250

Output Schema

NameRequiredDescriptionDefault
licenceNo
listingYes
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / pattern
      Previous value: -"^(?:SUB-[A-Z0-9-]{4,40}|BOE-B-\\d{4}-\\d{1,7})$"New value: +"^(?:SUB-[A-Z0-9-]{4,40}|BOE-B-\\d{4}-\\d{1,7}|TGSS-[A-Z0-9-]{4,40})$"
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Listing id, e.g. SUB-JA-2026-267510 or BOE-B-2026-35250"New value: +"Listing id exactly as returned by search_listings, e.g. SUB-JA-2026-267510 or BOE-B-2026-35250"
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds value on top: error behavior for delisted ids, data-freshness field (attribution.data_updated), disclaimer that risk analysis is not legal advice, and the critical note that bids/payments only happen on the official channel.

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?

Purpose and id formats are front-loaded in the first long sentence, followed by two short sentences on error behavior and the official-channel caveat. Dense but each clause adds information; slightly long.

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?

An output schema exists, so return values needn't be fully spelled out; the description still enumerates what's included (lots, deposit, deadline, bidding mode, risk analysis, links). Together with annotations this is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a regex pattern and example ids. The description adds the semantics of the prefixes (court auctions, BOE State sales, TGSS auctions), giving meaning beyond the pattern itself.

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?

States a specific verb ('Full record for one listing') plus the resource and the id-namespace conventions (SUB-, BOE-B-, TGSS-), which makes it clearly distinct from search_listings and get_facets.

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 signals the id must come 'from search_listings', implying the search-then-fetch workflow, and mentions an error if the id is no longer listed. No explicit when-not or alternative routing, but the context is clear.

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