Skip to main content
Glama

describe

Profiles tabular and tensor datasets to summarize schema, statistics, missingness, correlations, rank, and dimensionality, returning bounded outputs and a next-step recommendation.

Instructions

Budgeted profile of a dataset. For tables: schema, label columns, identifier-like and label-like integer columns, per-feature stats, missingness, constant and duplicated features, plus high-dimensional geometry on a sample: strongest correlations, effective rank, condition number, PCA components needed for 50/80/90/95/99% variance (on the chosen scaling AND on the other one), the number of correlation eigenvalues above the Marchenko-Pastur noise edge (how many factors carry more than noise), intrinsic dimension (TwoNN and MLE), distance concentration and hubness. standardize: 'auto' (default) keeps raw scales for data in one shared unit such as pixels / counts / [0,1] intensities and z-scores heterogeneous columns; True/False force it. For tensors: dims, coordinate ranges, fill rate per axis, value distribution. Ends with one consistent hint on what to do next.

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": "describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
seedNo
sampleNo
standardizeNoauto
max_featuresNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does convey that computation is sampled/budgeted and that scaling behavior depends on 'standardize'. It never states that the operation is non-mutating, nor how 'sample', 'seed', and 'max_features' change cost or determinism, so key behavioral levers remain unexplained.

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

Conciseness3/5

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

The core purpose is front-loaded in the first clause, which is good, but the middle is a dense comma-spliced inventory of statistics that is hard to scan. Several listed metrics (condition number, hubness, distance concentration) could be grouped or trimmed without losing decision-relevant information.

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?

An output schema exists, so return values need not be re-explained, and the description usefully splits table versus tensor behavior. However, for a five-parameter analytical tool it omits the meaning of most parameters and any note on cost, failure modes, or dataset-name requirements, leaving gaps an agent must guess at.

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% across five parameters, so the description must compensate and largely does not. Only 'standardize' is given real meaning ('auto' keeps raw scales for shared-unit data, z-scores heterogeneous columns, True/False force it); 'sample' is merely alluded to via 'on a sample', while 'seed' and 'max_features' are never addressed.

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?

Opens with a specific framing ('Budgeted profile of a dataset') and enumerates exactly what the profile contains for tables and tensors, so an agent knows the resource and the operation. It does not distinguish itself from siblings like 'plot' or 'loadings', which also surface statistical structure, leaving differentiation to inference.

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 reach for 'describe' rather than 'plot', 'loadings', or 'neighbors', and no prerequisites or exclusions. The only usage-adjacent text is the note that output 'ends with one consistent hint on what to do next', which describes the result rather than guiding tool selection.

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