Skip to main content
Glama
Sign In

site

by com.inductvo
OverviewDiscussionsAdmin

Summary statistics for a numeric column

dataset_stats

count, min, max, mean, median and sum of a numeric column of the Inductvo dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).

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": {
      "column": "<column>"
    },
    "name": "dataset_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It usefully reveals that grouping commas and currency symbols are handled and that non-numeric rows are excluded and counted. This goes beyond the title in explaining parsing behavior, though it does not cover all edge cases such as missing columns.

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, well-structured sentence that front-loads the returned statistics and then adds the important parsing caveats. Every clause adds value and there is no repetition of schema details.

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?

Given there is no output schema, the description adequately conveys the return values by listing the statistics. It also covers important data-cleaning behavior. It falls slightly short by not describing output format details or error behavior, but for a one-parameter tool this is largely sufficient.

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?

The schema provides only a required string 'column' with no description, and schema_description_coverage is 0%. The description adds meaning by specifying that the column must be numeric and referencing the Inductvo dataset, but it does not explicitly explain how column names are supplied or validated, leaving some inference required.

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?

The title and description clearly state that the tool computes summary statistics for a numeric column, explicitly enumerating count, min, max, mean, median, and sum. This makes the tool's purpose distinct from the sibling tools, which involve columns, comparison, provenance, rows, search, and top values.

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

Usage Guidelines3/5

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

The intended use is implied: call it when summary statistics for a numeric column are needed. However, the description does not explicitly explain when to prefer this over related tools such as dataset_top or dataset_search, nor does it state any exclusions.

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

All site toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources