Skip to main content
Glama
Podcast MCP
by calebn

record_state_tool

Read the live recording-room snapshot to check roster, take clock, consent, and unlanded-take status so producers can decide when to save finished recordings.

Instructions

Read the live recording-room snapshot (roster, take clock, consent, and the mint preflight: unlanded_take / unlanded_takes = stopped takes not yet saved to the episode, unlanded_saving = how many of those are still uploading or not started, unlanded_stalled = recordings that never finished uploading, land_first_possible = a prediction: true when a land could save a finished recording, nothing is saving and the room's session was not already accepted or skipped; false in such a decided room).

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_state_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "project_path"
      -]
  2. First observedv0.1.0

TDQS

B3.2/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; it does establish that this is a live read ('Read the live ... snapshot') with no mutation implied, and it defines the derived preflight fields precisely, which is real behavioral value. However, it says nothing about cost, whether the read is cached, permissions needed on the recording room, or any side effects of polling.

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?

The lead clause is correctly front-loaded with the resource, but the whole description is one sprawling sentence with a deeply nested parenthetical defining four derived fields inline. The field semantics earn their place, yet the run-on packaging makes it hard to scan and would read far better as a bulleted list of returned fields.

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 zero-annotation read tool with one optional parameter and an output schema, the definition is largely complete: it enumerates every returned field and explains the non-obvious derived ones (unlanded_*, land_first_possible) including the condition that makes the prediction false. The gap is the unexplained project_path scoping and the absence of any guidance on how this differs from get_session_state_tool.

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?

The single parameter project_path is undocumented at 0% schema coverage, and the description never mentions it at all — not what it identifies, nor what happens when it is omitted (default null). The description text covers only the return payload, so the caller must guess how to scope the call.

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?

Names a specific verb and resource ('Read the live recording-room snapshot') and enumerates exactly what the snapshot contains (roster, take clock, consent, mint preflight), so the agent knows what it gets back. It does not name or contrast with the obvious sibling get_session_state_tool, so the boundary between 'recording-room snapshot' and 'session state' is left for the agent to infer.

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?

Use is implied rather than stated: the detailed land_first_possible definition ('true when a land could save a finished recording...') suggests calling this before deciding whether to land, but the description never says 'call this before record_land_tool' or when to prefer it over get_session_state_tool. There are no explicit exclusions or prerequisites.

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