Skip to main content
Glama

Panel: column menu

column_menu
Read-only

Opens a column header menu in the results panel to show the source table column, whether it is kept from the AI, and its note.

Instructions

The results panel opens a column header's menu: the table column behind it, whether it is kept from the AI, and its note. App-only.

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": {
      "pull_id": "<pull_id>",
      "column": "<column>"
    },
    "name": "column_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
columnYes
pull_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful trait beyond that — 'App-only', signalling the tool only functions inside the app UI rather than headless/API contexts — plus what the panel surfaces, but it says nothing about whether opening the panel has side effects or what it returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single efficient sentence with no filler, which is appropriate for a small UI-panel tool. However, the clause order puts a confusing subject first and the three panel contents are listed as an afterthought colon list, so it is compact but not cleanly front-loaded.

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?

With no output schema and 0% parameter documentation, the description carries the full burden, yet it never explains what pull_id is, what the panel returns, or how the tool interacts with the related note/keep tools. For an app-only panel opener that is too thin.

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?

Schema description coverage is 0% for two required parameters. The description hints at 'column' via 'a column header's menu' but gives no format, identifier style, or example, and 'pull_id' is never mentioned anywhere in the description or schema.

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

Purpose3/5

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

The description names an action (opens a column header menu) and enumerates the panel contents (the table column, its kept-from-AI status, and its note), so the resource is identifiable. But the phrasing 'The results panel opens a column header's menu' makes the results panel the grammatical subject, obscuring that this tool is what performs the action, and it never distinguishes itself from nearby tools like column_note or keep_from_claude.

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 when-to-use guidance at all: nothing says whether to call this to inspect a column versus column_note to read/edit the note, or keep_from_claude to change AI visibility. 'App-only' is a constraint, not usage guidance, and no prerequisites or alternatives are offered.

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