Skip to main content
Glama

Data sources and dates

data_sources

Use when asked how current or how reliable the data is, or what it does not include. Which public files this data comes from, their snapshot dates, and what they do not cover.

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": "data_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. Framing the tool around "which public files this data comes from" and "snapshot dates" strongly implies a passive, read-only informational response, but it never states side effects, permissions, or the shape/format of the returned data. Adequate implication, no explicit behavioral guarantees.

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 short sentences, with the usage trigger front-loaded before the content summary. There is mild redundancy between "what it does not include" and "what they do not cover," which repeats the same idea rather than adding information.

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?

For a zero-parameter, no-output-schema informational tool, the description covers what the agent needs: when to reach for it and roughly what it returns (source files, snapshot dates, coverage limits). The absence of an output schema means the exact response structure is unknown, but that is a structural gap rather than a description failure.

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. Baseline 4 applies; the description correctly signals a no-input call by never referencing any filtering or scoping options.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource set — public source files, their snapshot dates, and coverage gaps — so the tool's output is identifiable as data-provenance metadata. It does not explicitly contrast itself with the sibling lookup/search tools, but those are clearly unrelated resources, so differentiation is implicit rather than stated.

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?

"Use when asked how current or how reliable the data is, or what it does not include" gives a concrete triggering condition tied to user question types. No exclusions or named alternatives are given, but there is no plausible sibling to confuse it with, so the guidance is sufficient in practice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.