Skip to main content
Glama

Find Target Relationships

find_target_relationships

Analyze relationships between numerical features and a target column, ranking features by correlation to identify key predictors for modeling.

Instructions

Analyze relationships between numerical features and a target column. Args: dataset_id (str): ID of the dataset. target_column (str): Name of the target column. Returns: dict: Features ranked by their correlation with the target.

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": {
      "dataset_id": "<dataset_id>",
      "target_column": "<target_column>"
    },
    "name": "find_target_relationships"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataset_idYes
target_columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden. It discloses the return content (a dict of features ranked by correlation with the target), which goes beyond the name, but it does not state which correlation method is used, how missing values or non-numeric columns are handled, whether the operation is read-only, or how many features are returned.

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 short and puts the core purpose first, then the Args and Returns. The docstring-style scaffolding is functional rather than wasteful, since the schema lacks descriptions. Overall the description is efficient.

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 two-parameter analysis tool, the description covers the purpose, the parameters, and the return shape, which is enough for an agent to call it correctly. The remaining gaps, such as the correlation method, the treatment of non-numeric columns, and the output size, are the most likely places for surprises.

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 0% and the schema gives only string types, so the description must compensate. It does so minimally: dataset_id as the 'ID of the dataset' and target_column as the 'Name of the target column'. No expected format is given, such as whether dataset_id is an ID or a name, and there are no constraints such as whether the target column must be numeric.

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 gives a specific verb and resource: 'Analyze relationships between numerical features and a target column', and it says what the result is (features ranked by correlation with the target). An agent can tell this is a target-focused correlation analysis. It does not, however, distinguish itself from siblings such as find_high_correlations or analyze_correlation.

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 when-to-use or when-not-to-use guidance and no named alternative. The phrase 'numerical features' implies that categorical data is excluded, but the agent must infer this and is not told whether to use a sibling such as find_high_correlations or analyze_categorical in that case.

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

Deploy Server

Other Tools