Skip to main content
Glama

Preview Parquet rows

preview_parquet
Read-onlyIdempotent

Return a slice of rows from a Parquet file (default 20, max 500), optionally only some columns, as JSON rows, a Markdown table, or CSV. Use to eyeball data; use query_parquet to filter or aggregate. Long cells are truncated. Price: $0.002 USDC per successful call, paid via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPublic http(s) URL of the input file. Preferred for anything over ~3 MB.
limitNoRows to return.
formatNojson rows (default), a Markdown table, or CSV text.json
offsetNoRows to skip.
columnsNoOnly these columns.
artifact_idNoartifact_id returned by an earlier convert_to_parquet call.

Output Schema

NameRequiredDescriptionDefault
rowsNoPresent when format=json.
textNoPresent when format=markdown or csv.
typesYes
columnsYes
row_countYes
truncatedYesTrue when more rows matched than were returned.
total_rowsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description adds material facts not in annotations: long cells are truncated, defaults/limits on row count, and that each successful call costs $0.002 USDC via x402 — a payment prerequisite an agent must know before invoking. It does not cover failure modes (bad URL, oversized file) or whether truncation is signalled in the output.

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?

Three tight sentences: capability first, routing to the sibling second, behavioural caveats (truncation, price) last. Nothing is repeated verbatim from the schema and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full output schema and complete annotation coverage, the description need not explain return values, and it correctly spends its words on limits, truncation, and cost. The one real gap is the unspecified input source (url vs artifact_id), which is the decision an agent most needs to make before calling.

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

Parameters3/5

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

Schema coverage is 100% and every parameter carries its own description, so the baseline is 3. The description restates default 20 / max 500 and the three formats but adds no new meaning, and notably does not explain the url vs artifact_id source choice — both are optional in the schema, so guidance on which to supply is missing from both structured and unstructured text.

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

Purpose5/5

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

States a specific verb and resource ("Return a slice of rows from a Parquet file") plus the shape of the result (JSON rows, Markdown table, or CSV), and names the sibling it is not (query_parquet). An agent can distinguish it from query_parquet, inspect_parquet, and convert_to_parquet without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives the selecting condition: "Use to eyeball data; use query_parquet to filter or aggregate." That is a clear when-to-use plus a named alternative with the condition that favours it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.