Skip to main content
Glama

Rename worksheet columns

bpj_table_rename
Read-onlyIdempotent

Apply a rename map in one pass and reject duplicate resulting field names.

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>",
      "mapping": "<mapping>"
    },
    "name": "bpj_table_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
mappingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive behavior. The description usefully adds that renames are applied in one pass and duplicate resulting field names are rejected, but it does not explain error behavior, handling of missing or unknown fields, or the response.

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 efficient sentence with the main behavior front-loaded. It has no filler, though it is arguably too terse for the undocumented parameters.

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

Completeness2/5

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

For a tool with two required parameters, zero schema descriptions, and no output schema, the definition leaves important input-format and failure-mode details unspecified. The annotations help with the safety profile, but the description is not complete enough for confident invocation.

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?

With 0% schema description coverage, the description must compensate for both required parameters. It references a rename map but does not explain the expected JSON structure of 'rows' or 'mapping', how old names are matched, or what happens to unmapped fields.

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 states a specific action: applying a rename map in one pass, with duplicate-result rejection. It is clear what the tool does, though the table/column scope is mostly carried by the title rather than the description.

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 guidance on when to use this versus alternatives, nor any stated preconditions or exclusions. Usage is only implied by the verb 'rename'.

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.