Skip to main content
Glama
Sign In

LyricPatch

by com.lyricpatch
OverviewDiscussionsAdmin

quote_generation

Idempotent

Get a fixed expiring quote without spending. Cost is ceil(seconds) per edit.

    max_credits is the user's authorized ceiling. Quote binds current lyrics/selections;
    changing an edit requires a new quote. Pass its id to generate_changes to spend.

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": {
      "project_id": "<project_id>",
      "edit_ids": "<edit_ids>",
      "max_credits": "<max_credits>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "quote_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
edit_idsYes
project_idYes
max_creditsYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare non-destructive and idempotent, and the description adds real behavioral context beyond them: the quote is fixed and expiring, it binds the current lyrics/selections, and billing is ceil(seconds) per edit. It does not disclose auth/permission requirements, but the lifecycle semantics are unusually well conveyed.

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?

Short and front-loaded: the key non-spending constraint leads, then the binding rule and the handoff instruction. The 'Cost is ceil(seconds) per edit' fragment is awkwardly placed but earns its space as pricing context.

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 spend/quote workflow is covered. The gap is on the input side: with four required parameters and no schema descriptions, several parameters are left semantically undefined.

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 carries the full burden, yet only max_credits is explained ('the user's authorized ceiling'). edit_ids is hinted at via 'binds current lyrics/selections', but project_id and idempotency_key get no semantic coverage in either place.

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+resource ('Get a fixed expiring quote') and immediately scopes it as non-spending, which separates it from the spender sibling generate_changes. Remains somewhat terse about what a quote actually is, but the resource and its lifecycle are identifiable.

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?

Explicitly tells the agent when to re-quote ('changing an edit requires a new quote') and what to do next ('Pass its id to generate_changes to spend'), naming the alternative tool and the handoff condition. This is complete routing guidance.

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

All LyricPatch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources