Skip to main content
Glama
EliyahuAI
by EliyahuAI

patch_column

Extend a validated research table by adding a new column. Preview cost estimate, then approve to run validation with caching for existing columns.

Instructions

Add a new column to a completed validation table.

If confirmed=False, returns a cost ceiling estimate (max-case: all rows x all columns x per_cell_cost x 1.25; likely much less if run within 1 day of original validation due to cache).

If confirmed=True, adds column header to source Excel, runs validation with updated config (old columns hit cache, new column fully validated), merges new column results into output Excel. No QC on column patch runs (single-column QC is not meaningful; full-table QC ran on the original validation).

Only available after full validation completes (status=completed).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesSession ID of a completed validation.
column_nameYesName of the new column to add.
validation_targetYesValidation target spec for the new column (same structure as config.validation_targets entries).
confirmedNoSet True to approve and trigger the ColPatch run. Set False (default) to see the cost estimate first.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description fully discloses behavioral traits: the cost estimate formula, caching behavior, merging of results, and lack of QC on patch runs. Annotations (readOnlyHint=false, destructiveHint=false) are consistent with the described non-destructive modification, and no contradictions exist.

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?

The description is concise with a front-loaded purpose statement and subsequent paragraphs explaining behavior in a logical flow. Every sentence adds necessary information without redundancy.

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 complexity (4 parameters, nested objects, output schema), the description covers all essential aspects: precondition (completed validation), two-phase execution, caching, cost estimation, and result integration. It is complete for an agent to determine correct usage.

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 adds value by explaining the 'confirmed' parameter's role in toggling between estimate and execution, and provides context for the cost calculation. For other parameters, the schema descriptions already suffice.

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 starts with 'Add a new column to a completed validation table,' which is a specific verb and resource. It clearly distinguishes this tool from siblings like start_table_validation or refine_config by focusing on adding a column after validation completion.

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 explains the two-mode behavior (confirmed=False for cost estimate, confirmed=True for execution) and explicitly states it is only available after full validation completes. However, it does not explicitly mention when not to use it or alternative tools for modifying existing columns.

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/EliyahuAI/mcp-server-subindex'

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