Skip to main content
Glama

Show kept rows

kept_rows
Read-only

Retrieve the rows returned by a past pull without rerunning it, as long as those rows were saved.

Instructions

Show the rows a past pull returned, if rows were kept for it (see keep_rows), without running it again.

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

Input Schema

NameRequiredDescriptionDefault
pull_idYes

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 already declare readOnlyHint and destructiveHint=false, so the safety profile is covered. The description adds two non-obvious behavioral facts: the underlying pull is not re-executed, and availability depends on rows having been kept — an agent can anticipate missing data. It stops short of saying what an unkept pull returns.

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?

A single sentence with no filler, front-loading the action and resource before the conditional and the sibling pointer. The nested qualifiers make it slightly denser than it needs to be, but nothing 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 one-parameter read tool with annotations covering the safety profile and no output schema, the description covers the essentials. The notable remaining gap is result shape and size — whether the kept rows are truncated or paginated — which matters for a rows-returning tool.

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?

There is one parameter, pull_id, at 0% schema description coverage, so the schema contributes only a title. The description conveys that the id refers to a past pull whose rows were kept, which is genuinely useful framing, but it does not state the id's origin or format beyond that.

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 verb and resource ('Show the rows a past pull returned') plus a clear scope qualifier ('if rows were kept for it'). It is immediately distinguishable from keep_rows and from rerun, which re-executes the pull.

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 definition sets an explicit precondition (rows must have been kept) and points to the sibling that creates that state ('see keep_rows'). It also implicitly rules out the rerun path with 'without running it again'. It does not spell out what to do when nothing was kept, so it falls short of a full when/when-not statement.

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