Skip to main content
Glama

Get Live Dataset Catalog & Freshness

get_catalog
Read-onlyIdempotent

Check live dataset freshness, indexed record totals, date coverage, and exact counts by registry section and notice type to confirm available data before querying tenders or funded companies.

Instructions

Retrieve live dataset freshness (data_version), total indexed records, earliest and latest publication dates (YYYYMMDD), and exact record counts grouped by registry section and notice type on datax-es.duckdns.org. Free read-only call requiring no DATAX_TOKEN. Call this to verify available sections and date coverage before querying with search_tenders or find_funded_companies.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
datasetsNo
total_returnedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "datasets": {
      +      "items": {
      +        "properties": {
      +          "counts_by_notice_type": {
      +            "type": "object"
      +          },
      +          "counts_by_seccion": {
      +            "type": "object"
      +          },
      +          "data_version": {
      +            "type": "string"
      +          },
      +          "doc_id": {
      +            "type": "string"
      +          },
      +          "earliest_fecha_pub": {
      +            "type": "string"
      +          },
      +          "latest_fecha_pub": {
      +            "type": "string"
      +          },
      +          "total_records": {
      +            "type": "integer"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total_returned": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: that the call is free and requires no DATAX_TOKEN (auth prerequisite), plus the YYYYMMDD date format of returned fields, which affects how an agent must interpret results.

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 returned data and followed by the usage trigger. Slightly dense enumeration of return fields that the output schema already documents, but no sentence is wasted.

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 zero params, full annotation coverage, and an output schema, the definition supplies everything essential: what it returns, that it is unauthenticated and free, and where it fits in the workflow. Rate limits or response-size expectations for a large catalog dump are the only notable omission.

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 takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema shows. Baseline 4 applies; the description correctly spends no words on parameters and instead covers scope.

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 (retrieve) and specific resources: dataset freshness (data_version), total indexed records, earliest/latest publication dates, and record counts by registry section and notice type. It even names the host, making it instantly distinguishable from the search/detail siblings.

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?

Explicitly says 'Call this to verify available sections and date coverage before querying with search_tenders or find_funded_companies', which gives a clear when-to-use condition and names the alternative tools it should precede. It stops short of stating when NOT to call it (e.g., if you already know the section), so not a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.