Skip to main content
Glama

Get the rows put in the chat

get_selection
Read-only

Fetches the exact rows and columns a user selected in the Portward results panel using a valid selection ID.

Instructions

Get the rows the user put in the chat from the Portward results panel: exactly the rows and columns they picked. Call it only with a selection id the user's message gave you ("use my selection sel_..."); don't guess ids or reuse a pull_id. You can read a selection again while it lasts (24 hours at most).

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": {
      "selection_id": "<selection_id>"
    },
    "name": "get_selection"
  }
}

Input Schema

NameRequiredDescriptionDefault
selection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnlyHint/destructiveHint=false annotations, it adds a real behavioral trait: the selection is readable repeatedly but expires after 24 hours. It also makes the return content clear ('exactly the rows and columns they picked'), so an agent knows both the lifetime and the shape of what comes back.

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 short sentences, front-loaded with what the tool returns before the invocation constraints and the TTL caveat. Every clause carries operational value; nothing repeats the title or the schema.

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

Completeness5/5

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

For a one-parameter, non-destructive read tool with no output schema, this covers everything an agent needs: where the id comes from, how long it stays valid, and what the response contains. No important gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description has to carry the parameter's meaning, and it does: it explains that selection_id must originate from the user's message and that its format looks like 'sel_...'. It also explicitly warns against substituting a pull_id, which closes the sharpest ambiguity for a lone string parameter.

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?

It names a specific verb and resource ('Get the rows the user put in the chat from the Portward results panel') and narrows the scope to 'exactly the rows and columns they picked', which distinguishes it from put_in_chat, kept_rows, and panel_rows without needing to open any schema.

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

Usage Guidelines5/5

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

It gives explicit invocation guidance: call it only with a selection id the user's message supplied, don't guess ids, and don't reuse a pull_id. That last prohibition is the key exclusion that would otherwise be a common mistake with a sibling tool.

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