Skip to main content
Glama

Keep result rows on or off

keep_rows

Toggle local retention of new query result rows; when enabled, rows are encrypted with an OS keychain key and stored for 30 days for later viewing.

Instructions

Turn keeping result rows on or off (off by default). When on, each new pull's rows are kept on this machine, encrypted with a key in the OS keychain, for 30 days; kept_rows shows them.

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": {
      "on": "<on>"
    },
    "name": "keep_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds genuinely new behavior: rows are stored locally, encrypted with an OS-keychain key, and expire after 30 days. The notable gap is what turning the setting off does to rows already kept — that materially affects how safely an agent should toggle it.

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?

Front-loaded with the action and the default, then the consequences and the sibling pointer. Nearly every clause earns its place; the only mild cramming is the semicolon-joined retention/encryption detail, but no wording is wasted.

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

Completeness4/5

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

For a single-boolean toggle with no output schema, the definition covers action, default, storage location, encryption, retention window, and the read path. Complete enough to call correctly, lacking only the effect of disabling on already-kept rows and any storage/quota caveats.

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 0%, so the description carries the burden, and it does: 'off by default' and 'when on, each new pull's rows are kept' give the boolean direct meaning in both states. It stops short of elaborating on timing (only new pulls are affected, which is stated) or any side effects of switching.

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?

States a specific action on a specific setting ('Turn keeping result rows on or off') and immediately differentiates it from the sibling that reads that data ('kept_rows shows them'). It also discloses the default state, so an agent knows the current baseline without calling anything.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: enabling retention is framed as what the tool does, and the reference to kept_rows hints at the read path. There is no explicit when-to-use/when-not guidance, no mention of privacy or storage trade-offs an agent should weigh, and no note on how to clear previously kept rows.

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