Skip to main content
Glama

Read current Clypmint workflows

get_workflow
Read-onlyIdempotent

Fuller notes for an unusual request: overview, music, styles, editing, publishing, capabilities. Read-only, free.

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

Input Schema

NameRequiredDescriptionDefault
topicNoWhich notes to read; overview when left out.overview

Output Schema

NameRequiredDescriptionDefault
codeNo
costNo
errorNo
stateNo
statusNo
dry_runNo
messageNo
plan_idNo
style_idNo
video_idNo
availableNo
import_idNo
output_idNo
studio_urlNo
version_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / topic / description
      Added value: +"Which notes to read; overview when left out."
  2. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds 'free' and indicates the notes are 'fuller', but repeats 'Read-only' and does not add auth, rate-limit, or return-format details beyond what the output schema provides.

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 description is very short and has no wasted sentences. However, the opening phrase 'Fuller notes for an unusual request' is less front-loaded than a direct statement of purpose would be.

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 simple optional-enum read tool with rich annotations and an output schema, the description plus schema cover topic selection and read-only/free behavior. The remaining gap is vague selection guidance, not missing invocation detail.

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 100%, and the topic enum is already documented in the schema. The description repeats the same six enum values but adds no per-topic meaning beyond the schema, so the baseline of 3 applies.

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

Purpose3/5

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

The description supplies content ('Fuller notes') and enumerates the six topics, but never defines what a 'workflow' note is or states the operation in a clear verb+object form. The title carries most of the meaning, and no sibling is explicitly distinguished.

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

Usage Guidelines2/5

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

Only 'for an unusual request' hints at usage, which is too vague to help an agent decide between this and siblings such as get_guide, project_notes, or get_basic_info. There are no when-not conditions or named alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources