Skip to main content
Glama

Panel: keep a column from the AI

keep_from_claude

Block a result column from AI access using its results-panel header; the rule applies from the next result onward.

Instructions

The user keeps a result column's table column from the AI, from its header in the results panel: a block rule, applied from the next result on. 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": "keep_from_claude"
  }
}

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 a non-read-only, non-destructive, closed-world operation. The description adds one genuinely useful behavioral fact beyond that — the rule is 'applied from the next result on', i.e. not retroactive — plus the app-only constraint, but says nothing about reversibility, permissions, or what is returned.

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 short sentence with no padding, but the phrasing is tangled ('keeps a result column's table column from the AI') and the key fact — that this creates a block rule — is not 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?

For a mutation tool that creates a persistent rule, with no output schema and no parameter documentation, the description should cover the pull_id, the effect on existing results, and how the rule can be undone or listed. It covers only the timing of the rule's effect.

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%, so the description carries the full burden. It gestures at the 'column' parameter via 'a result column's table column' and 'its header', but the required pull_id parameter is never mentioned, leaving half the inputs unexplained in both schema and prose.

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 phrase 'keeps a result column's table column from the AI' is awkward, but the clarifying clause 'a block rule' identifies the real action: creating a rule that excludes a column from AI processing. The verb is buried rather than stated, and nothing distinguishes it from siblings like block or keep_rows.

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?

It says where the action originates ('from its header in the results panel') and that it is 'App-only', but gives no guidance on when to use this versus block or keep_rows, and no prerequisites or exclusions.

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