Skip to main content
Glama

Analyze a table

analyze_table
Read-onlyIdempotent

Per-column statistics of a table: count, missing, distinct and type; min, max, sum, mean, median and standard deviation for numbers (numeric strings such as 1,5 included); most frequent values for text.

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": {
      "rows": "<rows>"
    },
    "name": "analyze_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesTable as an array of flat JSON objects (one per row), up to 500 rows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral detail beyond that: which statistics are computed for which inferred types, and notably that numeric strings such as '1,5' are coerced into numeric aggregation. It does not describe edge behavior for mixed or non-numeric columns, so it is not fully transparent.

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?

One dense, front-loaded sentence that enumerates the computed metrics with no filler. Ownership of space is near-optimal for a statistics tool.

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?

For a single-parameter, annotation-covered, non-destructive computation tool, the description is nearly complete: it tells the agent what outputs to expect without needing an output schema. The one gap is how values of ambiguous or mixed type are handled, which an agent might want to know before feeding heterogeneous data.

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 the single 'rows' parameter is documented in the schema as an array of flat JSON objects up to 500 rows. The description adds no further meaning about the parameter's shape or constraints, so the schema is doing all of the work; baseline 3 applies.

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 uses a precise resource framing ('per-column statistics of a table') and enumerates exactly which statistics are produced, so an agent knows what the tool does. It does not, however, distinguish itself from siblings like compare_tables or clean_table, leaving that inference to the agent.

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?

There is no statement of when to use this tool, when to prefer compare_tables or clean_table, or what preconditions apply (e.g., that the table must be passed inline as rows). The agent must infer applicability entirely from the description's vocabulary.

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.