Skip to main content
Glama
Podcast MCP
by calebn

record_target_tool

Sets where a room's recorded session lands—end, start, or a staged insert/replace suggestion—while target changes stay blocked once a take exists.

Instructions

Host Target: set where this room's session lands (end, start, or an insert/replace JSON object that stages the session as a suggestion; refused once a take exists).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "record_target_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoend
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real behavioral traits: the precondition (refused after a take exists) and the side effect that insert/replace values stage the session as a suggestion rather than applying it directly. It omits permissions, persistence of the setting, and whether end/start values commit immediately, leaving meaningful gaps for a mutation tool.

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?

A single dense sentence with the core operation front-loaded and the value enumeration and precondition packed into a parenthetical. Every clause carries information, though the backtick-heavy formatting and nested parentheses make it slightly harder to scan than it needs to be.

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?

An output schema exists, so return values need not be described, and the key refusal condition is covered. Still, `project_path` is unexplained and there is no routing guidance among the many record_* siblings, which for a two-parameter mutation tool leaves the definition only partially complete.

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. It explains the `target` parameter well by enumerating end, start, and insert/replace JSON objects and their staging semantics, but the second parameter `project_path` receives no mention at all, leaving half the surface undocumented.

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?

States a specific verb and object: 'set where this room's session lands', which is distinguishable from session-landing (record_land_tool) or take-discarding siblings. The parenthetical enumerates the accepted target values, so an agent can tell what the tool configures without opening the schema. It is slightly cryptic ('Host Target', 'lands') but not tautological.

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?

Provides one meaningful when-not condition: the operation is 'refused once a take exists', which tells the agent this must be set early. However, there is no explicit guidance on when to prefer this over related siblings such as record_land_tool, nor any prerequisite or ordering advice beyond that single constraint.

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