Skip to main content
Glama

Clean a table

clean_table
Read-onlyIdempotent

Clean a table: trim spaces, turn empty strings into null, remove duplicate rows, and optionally parse numeric strings (1,5 or 1 234) and normalize column names to snake_case. Returns the cleaned rows and a report.

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": {
      "rows": "<rows>"
    },
    "name": "clean_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesTable as an array of flat JSON objects (one per row), up to 500 rows.
trimNoTrim spaces (default true).
dedupeNoRemove duplicate rows (default true).
empty_to_nullNoEmpty strings become null (default true).
parse_numbersNoConvert numeric strings to numbers (default false).
normalize_keysNoRename columns to snake_case (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's real contribution is disclosing the return shape ("cleaned rows and a report") and the accepted numeric formats (1,5 and 1 234), which tell the agent it handles decimal-comma and space-grouped input. It still does not say what the report contains or how skipped/failed conversions are reported.

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 sentences, front-loaded with the verb and the operation list, then the return value. Every clause carries information and nothing is padded.

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 six-parameter, non-destructive utility with no output schema, the description covers purpose, operations, and return shape adequately; the 500-row cap and defaults live in the schema. Only the contents of the report remain ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns an extra point by giving concrete syntax examples for parse_numbers that the schema does not provide. The remaining toggles (trim, dedupe, empty_to_null, normalize_keys) are largely restated from the schema, including the snake_case naming.

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 verb+resource ("Clean a table") and enumerates the concrete transformations performed, so an agent can immediately tell this is data-hygiene work rather than analysis or conversion. It does not explicitly contrast with siblings like analyze_table or convert_data, keeping it short of a 5.

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 use case is implied (tidying raw rows before further processing) but never stated as guidance, and no alternatives or when-not-to-use conditions are named. An agent must infer that this precedes analyze_table/compare_tables rather than being told.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.