WiseGrid MCP

list_columns

List a sheet's columns to obtain their IDs, needed before writing data.

Instructions

List a sheet's columns. Cell dictionaries are keyed by these column IDs as strings, so you need them before any write.

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": {
      "sheet_id": "<sheet_id>"
    },
    "name": "list_columns"
  }
}

Input Schema

Name	Required	Description	Default
`sheet_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations provided, the description carries the full safety burden. It discloses that column IDs are used as string keys and that they are prerequisite for writes, which adds behavioral context beyond a simple 'list' phrasing, though it doesn't explicitly state the operation is non-mutating.

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 two sentences with no filler; the first sentence states the action, the second explains the value. Well-structured and front-loaded.

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?

For a simple read operation with an output schema, the description covers the essential guidance: what it does and why it's needed before writes. It doesn't complicate matters with edge cases, which are not critical here.

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

Parameters3/5

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

The schema provides only the parameter name and type (sheet_id integer) with no description (0% coverage). The description indirectly refers to it as 'a sheet' but does not explain the parameter's meaning or constraints. Given the single obvious parameter, the lack is a minor gap.

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 uses a specific verb ('List') and resource ('a sheet's columns'), clearly differentiating it from sibling tools like list_sheets and list_rows. It also provides a rationale that ties into subsequent write operations, reinforcing its distinct purpose.

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 states these column IDs are needed 'before any write', giving clear guidance on when to use this tool. It doesn't explicitly name alternatives, but for a list operation the use case is well-scoped.

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

Deploy Server