Skip to main content
Glama

suggest_cleaning

Read-only

Generates concrete, ordered cleaning steps with pandas code based on detected data issues; provides suggestions only without modifying files.

Instructions

Suggest concrete, ordered cleaning steps (with pandas code) based on find_issues. Suggestions only: no file is changed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description reinforces this with 'Suggestions only: no file is changed' and adds that output includes pandas code, but repeating the read-only property adds little new information and nothing is said about limits on suggestion scope or size.

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?

Two tight sentences with no filler, and the core capability (ordered cleaning steps with pandas code) is front-loaded before the read-only caveat. Every clause carries information.

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 simple, one-parameter, read-only tool with an output schema and clear annotations, the definition covers purpose, output nature, and non-mutation adequately. The only meaningful hole is the ambiguous 'name' argument, which is a modest gap given how little else the tool needs.

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?

There is a single parameter, 'name', with 0% schema description coverage, so the schema gives no meaning at all. The description only obliquely hints that the argument feeds find_issues; it never states whether 'name' is a dataset identifier, a file path, or a table name, so it fails to compensate for the coverage gap.

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 ('suggest') plus a concrete resource ('concrete, ordered cleaning steps with pandas code') and ties its output to find_issues, so an agent knows exactly what it produces. It also implicitly separates itself from a write/apply tool by saying no file is changed, though it never names such a sibling explicitly.

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?

'based on find_issues' implies the prerequisite step and the source of its input, which is useful ordering guidance. However, there is no explicit statement of when to prefer this over other profiling siblings (profile_dataset, quality_score) or what happens if find_issues was never run, so usage is only implied.

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