Skip to main content
Glama

Set how results reach the AI

set_send_mode

Switches a data source's result delivery: send rows directly to the AI after user confirmation, or show only the result shape until the user sends rows.

Instructions

Switch how a source's results reach you. 'results' (Claude gets results): you get the rows straight away, at most 200, minus the columns the user keeps from you; Portward asks the user to confirm. 'pick' (I send rows myself): you get only the result's shape until the user sends rows. Only call this when the user asks for it.

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": {
      "source": "<source>",
      "mode": "<mode>"
    },
    "name": "set_send_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
sourceYes

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 declare a non-read-only, non-destructive, closed-world mutation, and the description adds genuinely new behavior: real-time delivery is capped at 200 rows, user-hidden columns are stripped, Portward prompts for confirmation, and 'pick' mode withholds rows entirely. It does not say whether the setting persists for the source or how to revert it.

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?

The definition is short and front-loads the what before the constraint, so the key information is immediate. Inline glosses add a little density but each sentence carries distinct information.

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 non-destructive two-parameter mutation with no output schema, the description covers mode meanings, the confirmation step, and the row/column limits on delivery. The only real gap is the identity format of the required 'source' argument and whether the setting persists.

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

Parameters4/5

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

Schema coverage is 0% and neither parameter has an enum, so the description carries the full burden for 'mode', which it does by quoting the literal values 'results' and 'pick' and explaining each. The 'source' parameter is never explained (id vs. name, format), leaving one of two required inputs ambiguous.

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 description states a specific verb and resource ('Switch how a source's results reach you') and defines the two modes, so an agent knows exactly what the tool configures. It stops short of explicitly contrasting itself with sibling tools (e.g., keep_from_claude or kept_rows), which are in the same data-flow family.

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 closing sentence 'Only call this when the user asks for it' is an explicit usage constraint and an implicit restriction against proactive invocation. The mode descriptions also explain the consequences of each choice, which supports selection. What is missing is any guidance on which mode to prefer for a given user intent, since both are presented neutrally.

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