dataset_provenanceThe source, the date it was computed, the licence and the citation for the Tachovo 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?
No annotations are provided, so the description carries the full burden. It discloses the informational payload (source, computed date, licence, citation) and implies a read-only action via 'Read this', but it does not explicitly state that no side effects occur or whether the response is structured text or an object.
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 sentences with no filler. The key content is front-loaded, and the purpose statement is immediately actionable. The title also reinforces the description without being redundant.
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?
For a simple, parameterless metadata-access tool, the description is complete. It names exactly what information is available and why an agent would call it. No output schema is present, but the listed fields suffice for correct invocation and expectation-setting.
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?
The tool has zero parameters, so the schema already covers everything needed. The description adds no parameter details, but none are needed; a baseline of 4 is appropriate for a parameterless tool.
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 states exactly what the tool returns: source, date computed, licence, and citation for the Tachovo dataset. It also identifies the intended purpose ('attribute a figure correctly'), making it clearly distinct from siblings like dataset_search, dataset_stats, or dataset_compare.
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 gives a clear condition for use: read this when you need to attribute a figure correctly. It does not explicitly name alternatives, but the specialized provenance purpose is clear and distinct enough among the sibling list that confusion is unlikely.
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.
Each tool has a distinct purpose: schema, provenance, exact lookup, substring search, multi-value comparison, numeric stats, and top/bottom rows. The only possible confusion is between dataset_row and dataset_compare, since both match column values exactly, but the descriptions clarify single vs. multiple values.
All tool names share the dataset_ prefix and follow a consistent noun/feature pattern: columns, compare, provenance, row, search, stats, top. The convention is uniform and predictable.
Seven tools is well-scoped for exploring a single dataset. Each tool covers a distinct query mode or metadata need without redundancy or bloat.
The surface covers schema discovery, provenance attribution, exact matching, free-text search, multi-value comparisons, numeric statistics, and extremes. For a read-only dataset access server, this is a complete and practical toolkit with no obvious dead ends.