Skip to main content
Glama

Get a round of covers

get_cover_request
Read-onlyIdempotent

Each idea with its cover once drawn status: queued, drawing (covers appear as they are drawn), drawn, or failed (nothing charged; error says why). covers[].status: drawing, ready (cover: the cover kept on the song) or failed (it failed its check twice; not charged). credits: what the round cost.

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": {
      "request_id": "<request_id>"
    },
    "name": "get_cover_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesThe round id (coverreq_…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value by disclosing failure semantics ('nothing charged; error says why'), the double-check failure rule for covers, and that credits reflect the round cost — behavior an agent could not get from the schema or annotations.

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 text is dense and telegraphic, and every clause about statuses and billing earns its place, but it is not front-loaded with a purpose statement — it opens mid-thought with a status taxonomy. A single leading sentence on what is being fetched would make it much clearer without adding length.

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?

There is no output schema, so the description carries the full return-value burden, and it does so: it enumerates both idea-level and cover-level statuses, explains the 'ready' cover meaning, and clarifies credit accounting on failure. For a single-parameter polling tool, this is complete enough to interpret the response.

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?

With one parameter at 100% schema description coverage, the schema already documents request_id and its coverreq_… format. The description adds nothing about the parameter, 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 never states an action verb or what the tool returns as a whole; it is a glossary of status values. The name and title carry the purpose (fetch a cover round), and the content implies status retrieval, but the description itself would not distinguish this from a sibling on its own.

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?

There is no when-to-use guidance, no mention of polling until 'drawn', and no routing to alternatives such as list_song_covers or the request-creation tools. An agent must infer that this is the polling/status endpoint from the name alone.

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