Skip to main content
Glama

Get Live Dataset Catalog & Freshness

get_catalog
Read-onlyIdempotent

Verify available sections, date coverage, dataset freshness, and record counts 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-de.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.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description adds the two facts an agent could not infer: the call is free and requires no DATAX_TOKEN, and dates are formatted as YYYYMMDD. Disclosing auth requirements and cost is exactly the kind of behavior annotations cannot express.

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 front-loaded: the return payload comes first, then the call-to-action with alternatives. No filler or redundant restatement of the title.

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-parameter read tool with a full annotation set and an output schema, this covers everything: what it returns, its cost/auth profile, the date format, and where it sits in the workflow. Nothing an agent needs before calling 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 per the baseline this is a 4. The description describes return payload contents rather than parameters, which is appropriate here but leaves no parameter meaning to add.

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 names a specific verb and resource ('Retrieve live dataset freshness') and enumerates exactly what is returned: data_version, total indexed records, earliest/latest publication dates, and record counts grouped by registry section and notice type. It also names the host and distinguishes itself from siblings by directing querying work to 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?

It states the condition explicitly: 'Call this to verify available sections and date coverage before querying with search_tenders or find_funded_companies.' That gives both a when-to-use trigger and a sequencing rule relative to named alternatives.

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