Skip to main content
Glama

Inspect Parquet schema

inspect_parquet
Read-onlyIdempotent

Describe a Parquet file from its footer without reading rows: row count, columns, types, null counts, min/max per column, and SPSS/Stata/SAS labels. The cheapest way to understand a dataset before querying it. Input: artifact_id from convert_to_parquet, or a url to a .parquet file. 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": "inspect_parquet"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPublic http(s) URL of the input file. Preferred for anything over ~3 MB.
artifact_idNoartifact_id returned by an earlier convert_to_parquet call.

Output Schema

NameRequiredDescriptionDefault
rowsYes
columnsYes
created_byNo
row_groupsYes
size_bytesYes
key_value_metadataNoFile-level metadata, long values truncated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the description's real contribution is pricing and payment: $0.002 USDC per successful call via x402, which is a cost/auth trait no annotation conveys. It also clarifies that only the footer is read, implying low I/O cost, but says nothing about failure behavior for unreachable or invalid URLs despite openWorldHint=true.

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?

Four sentences, front-loaded with the capability and its output before positioning and input details. Nothing is redundant with the schema and no sentence could be dropped without losing information.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, annotations cover the safety profile, and both parameters are documented in the schema. For a read-only, two-optional-parameter inspection tool this is complete.

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 both parameters already carry descriptions, including the ~3 MB threshold for url and the artifact_id pattern, so the schema does the heavy lifting. The description restates the two input modes and adds only the minor clarification that url points to a .parquet file; baseline 3 is appropriate.

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 ('Describe a Parquet file from its footer') and enumerates exactly what is produced: row count, columns, types, null counts, min/max, and SPSS/Stata/SAS labels. The phrase 'without reading rows' plus 'understand a dataset before querying it' cleanly separates it from preview_parquet and query_parquet without needing to name them.

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

Usage Guidelines4/5

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

Gives a clear use context ('the cheapest way to understand a dataset before querying it') and tells the agent where the artifact_id comes from (convert_to_parquet) or that a direct .parquet URL works. It does not name an explicit when-not or a named alternative, which keeps it short of a 5.

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.