Skip to main content
Glama

About the dataset

dataset_info
Read-onlyIdempotent

Counts, last full check date, licence (CC BY 4.0), attribution text, download links, methodology page, and the latest monthly report on AI-agent access in Spain (https://agentbrokerindex.com/es/informe/2026-11/) with its headline findings.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety and repeatability profile is fully covered structurally. The description adds that a 'last full check date' is part of the payload, which is useful freshness context, but it says nothing about formatting, size, or how the embedded report link is meant to be used. The odd, time-stamped external URL (2026-11) is presented without explanation and reads as promotional rather than behavioral.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Everything is crammed into a single run-on sentence that mixes static metadata (licence, attribution, download links) with a specific dated report and an inline URL. No structure separates the durable dataset facts from the time-sensitive report pointer, and the URL occupies a large share of the text without earning its place in a tool description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must explain the return payload, and it makes a genuine attempt by enumerating the fields. However, the enumeration is partial and unstructured ('counts' of what? which download links?), and inclusion of a specific external report invites an agent to treat volatile marketing content as tool output. Adequate but incomplete for a tool whose only contract is the shape of what it returns.

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 applies. The listed content items do not correspond to any inputs, which is consistent with a parameterless call.

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

Purpose3/5

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

The description is a noun-phrase inventory of returned content (counts, last check date, licence, links, methodology, monthly report) rather than a statement of what the tool does. Combined with the name 'dataset_info' and title 'About the dataset', an agent can infer it returns dataset metadata, and it is clearly distinct from the provider-oriented siblings. But the absence of a verb leaves the purpose inferred 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 Guidelines2/5

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

There is no guidance on when to call this tool, when not to, or in what situation it should precede the provider tools. The sibling list (compare_providers, get_provider, list_changes, search_providers) contains plausible related tasks such as verifying data provenance or licence before citing results, but the description never makes that connection.

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.