Skip to main content
Glama

analyze_correlations

Computes Pearson or Spearman correlations for a CSV dataset and returns top variable pairs, helping identify relationships before modeling.

Instructions

Compute numerical correlations and strongest pairs.

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

Input Schema

NameRequiredDescriptionDefault
nameYesDataset filename.
top_nNoNumber of top pairs to return (default 10).
methodNo'pearson' or 'spearman' (default pearson).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only analysis operation but does not state whether the dataset must be numeric, how missing values are handled, what the output looks like, or any permission or performance considerations.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no unnecessary wording. However, the phrase 'strongest pairs' is slightly compressed and could be clearer about what is being paired.

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

Completeness2/5

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

The tool is simple with three well-documented parameters, but no output schema exists and the description does not explain return values or assumptions. For a dataset analysis tool with no annotations, this leaves important context missing.

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 description coverage is 100%, so all three parameters are already documented with defaults and allowed values. The description adds only a general sense of 'strongest pairs' corresponding to top_n, without meaningful detail beyond the schema.

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 specific verb, 'Compute', and names the resource, 'numerical correlations and strongest pairs'. This clearly distinguishes the tool from unrelated siblings such as compare_models or train_baseline, though it does not explicitly contrast with analyze_data_quality or other analysis tools.

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 explicit guidance on when to use this tool versus alternatives such as analyze_data_quality or predict. The implied context is dataset correlation analysis, but the description provides no conditions, prerequisites, or exclusions.

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