Skip to main content
Glama

Panel: read a pull's rows

panel_rows
Read-only

Reads a pull's rows for the results panel while keeping the returned data app-only and hidden from the model.

Instructions

The results panel reads a pull's rows. App-only: the model never sees this result.

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

Input Schema

NameRequiredDescriptionDefault
pull_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds information annotations cannot express: the result is consumed by the app UI and is never surfaced to the model, which materially changes whether an agent should call it at all. It does not say what happens with a missing or invalid pull_id.

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?

Two short sentences, no filler, and the most decision-relevant fact (the model never sees the result) is placed second where it still reads clearly. Nothing could be removed without losing meaning.

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

Completeness3/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 no output schema, the definition covers purpose and the app-only constraint. It leaves open what a row contains, whether the set is paginated or truncated, and what error behavior looks like, which matters because an agent has no output schema to fall back on.

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 must carry the load for pull_id. It only implies that pull_id designates the pull whose rows are read; there is no format, source, or validity guidance. For a single required identifier this is the minimum acceptable, not more.

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?

"The results panel reads a pull's rows" gives a concrete verb (reads) and resource (a pull's rows) and scopes it to the results panel UI surface. It does not differentiate from near-neighbours like kept_rows or more_rows, so an agent cannot tell from this text which row-reading tool applies in which situation.

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?

"App-only: the model never sees this result" strongly implies the model should not be the caller and would get no usable return value, which is real usage context. But it stops short of an explicit directive ("call only from the app UI; never invoke from a tool-calling loop") and names no alternative tool for reading rows.

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