dataset_columnsThe columns, which of them are numeric, the row count and the provenance banner of the Lanyardo dataset. Call this first to learn the schema.
| 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 full burden. It discloses the exact content returned (columns, numeric flags, row count, provenance banner), which is transparent for a read-only schema tool. It does not mention response format or side effects, but for a zero-parameter tool, this is adequate.
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 a single, compact sentence that efficiently communicates the tool's output and usage. It front-loads the key information and includes the 'call first' directive without any fluff.
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 fully covers the tool's functionality for a schema-introspection tool with no parameters. It specifies the data returned and the recommended usage, which is sufficient for an agent to invoke it correctly. The absence of an output schema is compensated by the clear enumeration of what the tool provides.
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 description doesn't need to explain any. According to the baseline, a 4 is appropriate since there are no parameters to document.
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 the tool returns the columns, numeric flags, row count, and provenance banner of the Lanyardo dataset, which is a specific and clear purpose. It also distinguishes itself from siblings like dataset_stats and dataset_provenance by focusing on schema learning.
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 explicitly instructs to 'Call this first to learn the schema,' providing clear when-to-use guidance. It does not explicitly contrast with alternatives, but the 'first' positioning implies precedence over other dataset tools.
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 inspection, exact match lookup, substring search, comparison of multiple values, stats computation, top/bottom ranking, and provenance metadata. There is no ambiguity about when to use which tool.
All tools follow a uniform 'dataset_' prefix followed by a descriptive noun or verb (columns, compare, provenance, row, search, stats, top). The naming pattern is consistent and predictable.
Seven tools is well-scoped for a dataset querying server. Each tool covers a distinct operation without redundancy, and the count feels neither sparse nor bloated.
The surface covers schema discovery, data retrieval via exact match, substring search, multi-value comparison, numeric statistics, top/bottom ranking, and provenance. For a read-only dataset server, this is a complete set with no obvious gaps.