Skip to main content
Glama

Panel: put rows in the chat

put_in_chat

Sends a results-panel selection to chat by row positions and column names, returning only the selection ID—not its values—so users can reference data without exposing it.

Instructions

The results panel records the user's selection (row positions, column names) and gets the short chat message it posts: the selection's id, never its values. App-only.

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>",
      "rows": "<rows>",
      "columns": "<columns>"
    },
    "name": "put_in_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnsYes
pull_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is known. The description usefully adds that only the selection's id — never its values — is written, which is meaningful privacy context absent from the annotations, plus an "App-only" availability constraint. It still omits whether the message is persistent, what happens on repeat calls, and what the call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no filler, but the two clauses are compressed into a run-on construction that forces re-reading, and the most important fact (id only, never values) sits at the end rather than being front-loaded.

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

Completeness2/5

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

For a three-parameter mutation tool with no output schema and no parameter documentation anywhere, the definition leaves too much open: pull_id is unexplained, the notion of "the chat" is undefined, and the effect on the user's view is unstated. The one behavioral detail it does give (id, not values) shows the right instinct but is not enough.

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

Parameters2/5

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

Schema description coverage is 0% across three required parameters, so the description carries the full burden. It partially glosses rows as "row positions" and columns as "column names", but pull_id is never mentioned and no formats or constraints are given for any of the three.

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

Purpose3/5

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

The description names the resource (the results-panel selection) and states it records row positions and column names and posts a short chat message with the selection's id. However, the verb is split and oddly phrased ("records ... and gets the short chat message it posts"), leaving it unclear whether the tool sends a message, returns one, or both. Nothing distinguishes it from siblings like keep_rows or panel_rows.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. "App-only" is a scope/environment constraint rather than invocation guidance, so the agent must infer the trigger condition entirely.

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