Skip to main content
Glama
Podcast MCP
by calebn

select_session_take_tool

Chooses the take a pending replace session will apply, letting you review or change the edit before accepting it.

Instructions

Pick the take a pending replace session will place (one undo step).

Accept and hear_session_suggestion_tool use it unless given another take_index. Refuses a session that is not pending (session_suggestion_not_pending), an unknown take (take_not_found), an insert (take_not_applicable), a track the take did not record (track_not_recorded), a range that changed (stale_anchor) and anything else accepting that take refuses. Choosing the take already chosen changes nothing.

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": {
      "suggestion_id": "<suggestion_id>",
      "take_index": "<take_index>"
    },
    "name": "select_session_take_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
take_indexYes
project_pathNo
suggestion_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses reversibility ('one undo step'), idempotency ('choosing the take already chosen changes nothing'), and an unusually complete list of refusal conditions with their error identifiers (session_suggestion_not_pending, take_not_found, take_not_applicable, track_not_recorded, stale_anchor). This is exactly the behavioral context an agent needs before invoking a state-changing selection.

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?

Front-loaded with the core action in the first sentence, then the conditional relationship, then failures and idempotency. The refusal list is dense and slightly run-on, but every clause carries information an agent would otherwise have to discover by trial.

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?

An output schema exists, so return values need not be described, and the behavioral surface (refusals, idempotency, undo scope) is well covered for a 3-parameter mutating tool. The main gap is the unexplained project_path parameter, which neither the description nor the schema clarifies.

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 description coverage is 0%, so the description must compensate, and it only partially does: take_index is referenced ('given another take_index'), and the failure modes imply what suggestion_id and take_index address. project_path is never mentioned in the description or the schema, leaving one of three parameters unexplained.

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 first sentence names a specific verb (pick) and resource (the take a pending replace session will place), plus the consequence ('one undo step'). It is clearly distinct from accept_session_suggestion_tool and hear_session_suggestion_tool, though 'pending replace session' is domain jargon an agent must infer from elsewhere.

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 description states that accept and hear_session_suggestion_tool use this selection unless given another take_index, which effectively tells the agent when this choice matters. It stops short of an explicit sequencing instruction such as 'call before accepting' and gives no guidance on when to skip selection entirely.

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

Deploy Server

Other Tools