Skip to main content
Glama

preview_rows

Read-only

Preview up to 20 rows of a dataset exactly as stored to inspect raw values before profiling, issue detection, or cleaning.

Instructions

Return the first n rows of a dataset exactly as stored (n is capped at 20).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "preview_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare this as a safe read-only, non-destructive operation. The description adds useful behavioral context beyond the annotations: the row cap of 20 and the guarantee that rows are returned exactly as stored rather than transformed or cleaned.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no redundant wording. The row cap, a key constraint for invoking the tool correctly, is included without padding.

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?

This is a simple read-only preview tool, and the output schema and annotations already cover return values and safety behavior. However, the description still omits parameter documentation for name and does not indicate when to prefer this tool over the sibling profiling or listing tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for both parameters. It explains n and its cap, but it leaves the required name parameter largely undocumented beyond implying it is the dataset name, with no detail about acceptable format or whether it is a name or identifier.

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

Purpose4/5

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

The description states a specific verb and resource: return the first n rows of a dataset. That is clear enough to distinguish it from profiling or listing tools, but it does not explicitly name a sibling or describe the boundary between previewing and profiling.

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?

It gives no explicit guidance on when to use this tool versus alternatives such as profile_dataset or list_datasets. The intended quick-preview use is implied, but the description does not state when this tool should or should not be chosen.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.