dataset_provenanceThe source, the date it was computed, the licence and the citation for the Huddlevo dataset. Read this to attribute a figure correctly.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It discloses the returned content but does not mention side effects, authentication, or failure modes. However, as a read-only metadata tool, the description is minimally adequate but could be more explicit about the return format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no fluff. The core content is front-loaded, and the usage hint is clear.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description lists the key provenance fields and the purpose (attribution). It lacks the exact structure of the response, but for a simple metadata tool, it's largely sufficient. Given no output schema, a bit more detail on the response format would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, and the schema is empty. Per the baseline for zero parameters, a score of 4 is appropriate since no parameter documentation is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the tool provides the source, computed date, licence, and citation for the Huddlevo dataset. This clearly differentiates it from sibling tools that handle columns, comparisons, rows, searches, statistics, and top-level views.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description instructs the agent to read this when attributing a figure correctly, providing a clear use case. It doesn't explicitly mention alternatives, but the context of siblings makes it obvious this is for provenance, not data manipulation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly separated by query type: exact match, contains search, compare, stats, top, schema, and provenance. There is minor overlap between dataset_row and dataset_compare for simple equality lookups, but the descriptions make the intended use clear enough.
All tools share the dataset_ prefix and use snake_case, which creates a predictable family. However, the second part mixes nouns (columns, provenance, row, stats), verbs (compare, search), and adjectives (top), so it is not a strict verb_noun convention.
Seven tools is a well-scoped number for a single-dataset query interface. Each tool addresses a distinct common question type, and none feel redundant or excessive.
The set covers schema discovery, exact value lookup, substring search, multi-value comparison, numeric statistics, extreme values, and provenance. Minor gaps include no distinct-values tool and no paginated full-table retrieval beyond the 50-row search cap, but core exploration workflows are supported.