dataset_provenanceThe source, the date it was computed, the licence and the citation for the Take-Home Compass 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?
The description states exactly what information the tool provides (source, date computed, licence, citation) and implies a read-only, side-effect-free operation. No annotations exist, but nothing in the description contradicts observable behavior.
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?
The description is brief and well-structured, using two sentences to convey both content and usage. No unnecessary words or redundancy.
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 parameterless provenance tool, the description is complete: it names the dataset, lists the returned attributes, and explains when to use it. An explicit return schema is absent, but the listed attributes provide enough context for this simple tool.
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 and the schema coverage is 100%, so the baseline of 4 applies. Since there are no parameters to describe, the description sufficiently covers the parameter space.
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?
Clearly identifies the resource (Take-Home Compass dataset provenance) and the specific purpose (to attribute a figure correctly). The title and description align well, and the tool is distinguishable from sibling tools focused on columns, search, stats, etc.
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?
Explicitly tells the agent when to use it ('Read this to attribute a figure correctly'), implying use when citation or provenance information is needed. It does not explicitly contrast with sibling tools, but the purpose is specific enough 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 clearly distinct purpose: schema, provenance, exact-row lookup, substring search, multi-value comparison, aggregate stats, top/bottom ranking, and enquiry lifecycle steps. Even the three query tools (dataset_row, dataset_compare, dataset_search) are semantically separate and described with enough precision to avoid misselection.
All tools follow a consistent snake_case pattern with a domain prefix: dataset_* for the data exploration tools and enquiry_* for the form workflow. The suffix is sometimes a noun (columns, provenance, fields) and sometimes a verb (search, compare, submit), but the uniform prefix and predictable structure make the set easy to navigate.
Ten tools is a well-scoped size for a server covering two related areas: dataset analysis and enquiry submission. Each tool earns its place; there is no obvious redundancy or bloat, and the split of seven dataset tools and three enquiry tools matches the apparent purpose.
The dataset tools cover schema discovery, provenance, filtering, searching, comparison, statistics, and ordering—a solid analytical surface. The only notable gap is a way to retrieve all rows at once without a filter, though that may be intentionally omitted since most queries are targeted. The enquiry tools form a complete describe-fields-submit flow.