Skip to main content
Glama

Get Live Dataset Catalog & Freshness

get_catalog
Read-onlyIdempotent

Retrieve live dataset freshness, indexed record counts, and publication date coverage by section and notice type to verify available data before running tender searches or funded-company queries.

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-it.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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds non-redundant context the annotations do not carry: the call is free and requires no DATAX_TOKEN, which is real auth-cost information for an agent deciding whether to spend a call. It stops short of describing pagination, response size, or rate limits, so it is strong but not exhaustive.

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?

Two sentences, both load-bearing: the first defines the returned payload, the second gives the call-ordering rule. The most decision-relevant fact (free, no token) and the date format are front-loaded rather than buried, and there is no restatement of the title or name.

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?

An output schema exists, so return values need not be exhaustively explained; the description nonetheless names the key fields an agent would use to plan a follow-up query (sections and date coverage). For a zero-parameter, read-only metadata tool, nothing needed 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 with additionalProperties=false, so there is nothing for the description to disambiguate and the baseline applies. The description correctly adds no parameter guidance and instead spends its words on return content, which is the right allocation for a no-arg tool.

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?

Opens with a specific verb and resource ('Retrieve live dataset freshness') and 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 names the host datax-it.duckdns.org, so the agent knows this is a catalog/metadata endpoint rather than a record search, distinguishing it from search_tenders and find_funded_companies.

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?

Explicitly states the sequencing rule: 'Call this to verify available sections and date coverage before querying with search_tenders or find_funded_companies.' It names two concrete alternatives and the condition that makes this tool the right first step, rather than leaving the agent to infer it.

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