Skip to main content
Glama

Send more rows

more_rows
Read-only

Fetch additional rows from a pull when the preview is insufficient; requires user approval before sending more rows (100 by default, up to 500).

Instructions

Send more rows of a pull than its preview. The user is asked first, every time; only call this when the preview isn't enough. rows is how many more (default 100, at most 500). Set approved only after you asked the user the question this tool gave you and they said yes.

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": "more_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNo
pull_idYes
approvedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare it a safe read; the description adds the material behavior that a user prompt is raised on every call and that `approved` must be set only after that question is answered affirmatively. The 500-row ceiling is also disclosed. It stops short of saying what happens when `approved` is false or whether repeat calls re-prompt.

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?

Three tight sentences, front-loaded with the action and the usage gate before parameter detail. Every sentence adds a rule the agent needs; nothing is restated from the schema titles or annotations.

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 three-parameter, non-destructive read with no output schema, the definition covers the trigger condition, the human-approval protocol, and the row-count bounds. Only the outcome of a declined or partial approval is left unstated.

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?

Schema coverage is 0%, so the description carries the load, and it does explain `rows` (meaning, default 100, hard cap 500) and the conditional rule for `approved` — real value beyond the bare titles. `pull_id` is left undefined, though its meaning is reasonably inferable from the tool's purpose.

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

Purpose4/5

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

States a specific verb and resource: 'Send more rows of a pull than its preview', which pins down both the action and its relation to the preview. It doesn't name a sibling tool, but the 'than its preview' framing makes the boundary clear enough to distinguish it from a preview call.

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?

Explicit gate: 'only call this when the preview isn't enough', plus the requirement that the user is asked first every time. That gives a clear when-to-use and a precondition the agent must satisfy. What's missing is any named alternative for cases where the agent wants a different slice of data.

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