Skip to main content
Glama

HammerMap: Spanish court, State and Social Security auctions

Filter values, counts and data freshness

get_facets
Read-onlyIdempotent

Counts of active listings (bid deadline not passed) by type, procedure, asset type and province, the starting-price range, covered countries, and data freshness (data_updated, latest_boe_publication, update_frequency). Use it to discover valid filter values for search_listings or to answer "how many / how fresh" questions. No arguments.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
facetsYes
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With annotations already covering read-only, idempotent, non-destructive, and closed-world behavior, the description adds useful scope: only active listings whose bid deadline has not passed, plus the freshness fields returned. It does not need to explain return shape because an output schema exists.

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 front-loaded with what the facet counts cover, then gives the use case and the no-arguments note. The sentences are dense but every clause provides relevant scope or routing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-argument read-only aggregator with a full output schema and rich annotations, the description covers purpose, scope, freshness, and intended use. No additional behavioral detail is required for an agent to invoke it correctly.

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?

The tool has zero parameters, so the baseline is 4. The description's 'No arguments' is consistent with the empty input schema and leaves no parameter ambiguity.

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 aggregation resource: counts of active listings by type, procedure, asset type, province, starting-price range, covered countries, and freshness fields. This clearly distinguishes it from get_listing and search_listings, which retrieve listings rather than facet/count data.

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 explicit positive use cases: discovering valid filter values for search_listings and answering how-many/how-fresh questions. It does not explicitly state when not to use it, but the aggregation purpose and named link to search_listings provide clear routing context.

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