Skip to main content
Glama
Sign In
Cyan Eclipse Cadence MCP

Cyan Eclipse Cadence MCP

Official
by CYAN-ECLIPSE-TECHNOLOGIES-LLC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List stored Cadence render records

cadence_renders_list

Lists stored Cadence render and acceptance records with IDs, episode, take, voice, duration, state, and in-band percentage so you can find a valid record_id before reading details.

Instructions

List Cadence's stored render and acceptance records with record_id, episode, take, voice, duration_s, state, and in_band_pct. Use this first to discover a valid record_id for cadence_renders_read. These are historical stored records, not live render status; this tool cannot start, retry, or inspect an in-progress synthesis. Behaviour: local file reads only, with no network, authentication, credentials, or audio playback; a successful call appends a content-minimal hash receipt. Returns an object with renders, receipt_id, and receipt_head, with null fields where a record does not carry a value.

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": "cadence_renders_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
rendersYes
receipt_idYesIdentifier of the content-minimal receipt appended for this successful call.
receipt_headYesHash head of the facade receipt chain after this call's receipt was appended.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by explaining that the operation is local file reads only, with no network, auth, credentials, or playback, and that a successful call appends a content-minimal hash receipt. That receipt side effect actually explains why readOnlyHint is false despite this being a listing operation, resolving a potential confusion an agent would otherwise have.

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?

Three dense, front-loaded sentences that each carry real information: contents, routing to the read tool, exclusions, side effects, and return shape. The return-shape sentence partly overlaps the output schema, but the null-field note adds value, so only minor trimming is possible.

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

Completeness5/5

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

Given a zero-parameter tool with an output schema, the description covers purpose, routing, exclusions, side effects, and null semantics. Nothing an agent needs in order to call it correctly is missing.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline is 4. The description correctly focuses on output fields and discovery behavior instead of inventing parameter guidance.

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

Purpose5/5

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

States a specific verb and resource ("List Cadence's stored render and acceptance records") and enumerates the fields returned, so an agent knows exactly what it gets. It also distinguishes itself from cadence_renders_read by positioning itself as the discovery step.

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

Usage Guidelines5/5

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

Explicit when-to-use: "Use this first to discover a valid record_id for cadence_renders_read." Explicit when-not-to-use: historical records only, cannot start, retry, or inspect in-progress synthesis, which implicitly routes those needs to other siblings like cadence_render_propose.

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