Skip to main content
Glama

Get Live Dataset Catalog & Freshness

get_catalog
Read-onlyIdempotent

Retrieve live dataset freshness, indexed record totals, publication date ranges, and counts by registry section and notice type to verify coverage before searching 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-pt.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.1
    • 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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds value the annotations cannot: the call is free and requires no DATAX_TOKEN, which is real auth/cost information an agent needs before deciding to call it. It stops short of mentioning rate limits or pagination, but with no parameters those concerns are minimal.

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, each earning its place: the first lists returned fields, the second gives the auth/cost fact and the usage rule. The return-field enumeration is somewhat list-dense and partially duplicates the output schema, which keeps it from a 5, but it is front-loaded and free of filler.

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?

A zero-parameter, read-only catalog call with an output schema and full annotation coverage — the description supplies the only things structured fields could not convey (free, no token, call before querying). Nothing an agent needs in order to invoke it correctly is missing.

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 object schema already states. Baseline of 4 applies.

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?

Names a specific verb ('Retrieve') and a concrete resource (live dataset catalog/freshness on datax-pt.duckdns.org), then enumerates exactly what comes back: data_version, total indexed records, earliest/latest publication dates in YYYYMMDD, and per-section/per-notice-type counts. It also explicitly separates itself from search_tenders and find_funded_companies, so an agent need not open any schema to know which tool it is holding.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States an explicit ordering rule: call this to verify available sections and date coverage *before* querying with search_tenders or find_funded_companies. That names the alternatives and the condition that selects this one, which is stronger than the usual 'use this to get the catalog' guidance.

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