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 registry section and notice type to verify sections 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-fr.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, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds genuinely new operational context: the call is free and requires no DATAX_TOKEN, plus the host it hits. It stops short of describing response size or caching behavior, but with an output schema present that gap is minor.

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, both working hard, with the identity/host front-loaded and the usage directive last. The long enumeration of returned fields slightly overlaps the output schema, but it usefully signals what an agent gets before it opens the schema.

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-only catalog call with rich annotations and an output schema, the description covers everything needed to decide and invoke: what returns, what it costs, what auth is not needed, and when to call it. No material omission remains.

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 no parameter meaning for the description to supply; the baseline applies. Nothing in the description misleads about inputs, and it correctly implies a no-argument call.

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?

Specific verb 'Retrieve' paired with a clearly bounded resource: freshness, record totals, publication-date range, and counts by section/notice type on a named host. The enumeration of returned fields makes it instantly distinguishable from search_tenders and find_funded_companies, which query rather than summarize coverage.

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 explicitly when to call it ('verify available sections and date coverage before querying') and names the two downstream tools it should precede. The ordering constraint is the exact guidance an agent needs to sequence this call correctly.

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