Skip to main content
Glama

compare_profiles

Compare two dataset profiles to identify differences in rows, columns, null counts, data types, and duplicates. Get a human-readable summary of changes between original and cleaned data.

Instructions

Compare two dataset profiles and produce a side-by-side diff.

Pass the JSON strings returned by profile_dataset() for the original
and cleaned files. Returns rows added/removed, columns added/removed,
null count changes per column, type changes, and a human-readable summary.

Args:
    before_profile: JSON string from profile_dataset() on the original file.
    after_profile:  JSON string from profile_dataset() on the cleaned file.

Returns JSON with: row_delta, col_delta, column_diffs (nulls, dtypes),
duplicate_delta, and a human_summary string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
before_profileYes
after_profileYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/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. It discloses inputs (two JSON strings), outputs (a JSON with specific fields), and implies a read-only comparison with no side effects. It does not mention authentication or rate limits, but the overview is adequately transparent for a comparison tool.

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 paragraph but effectively covers purpose, arguments, and returns. It is concise without unnecessary words, though it could benefit from bullet points for improved readability. It earns its place with informative content.

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

Completeness5/5

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

Given the tool has an output schema (mentioned in context), the description does not need to elaborate on return values but still describes the return structure. The two parameters are well-documented, and the tool fits logically among siblings like profile_dataset. The description is complete for an agent to use effectively.

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

Parameters5/5

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

With schema description coverage at 0%, the description fully explains both parameters: before_profile as a JSON string from profile_dataset() on the original file, and after_profile similarly for the cleaned file. This adds crucial context beyond the schema's basic type definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool compares two dataset profiles and produces a side-by-side diff, listing specific outputs (rows/columns added/removed, null count changes, type changes). This distinguishes it from related tools like profile_dataset (which generates a profile) and clean_dataset (which cleans data).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs to pass JSON strings from profile_dataset() for original and cleaned files, implying usage after profiling. It does not provide explicit 'when not to use' or alternatives, but the context is clear and sufficient for selecting this tool among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis_PH'

If you have feedback or need assistance with the MCP directory API, please join our Discord server