Skip to main content
Glama

get_process_result

Read-only

Free. Status and file URLs of process_song / voice_cover. For wav pass the song id; for vocals / stems / midi / voice_cover pass the id that tool returned.

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": {
      "action": "<action>",
      "id": "<id>"
    },
    "name": "get_process_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description still adds real value beyond that: 'Free' tells the agent no credits are consumed, and the id-routing rule discloses a non-obvious behavioral dependency on the upstream tool's return value. It stops short of describing status values, polling behavior, or failure modes when a job isn't ready.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the cost fact ('Free.') then purpose, then the parameter rule. No filler; every clause carries information the agent needs.

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 2-parameter read tool with no output schema, this covers what is returned (status and file URLs), what it costs (nothing), and how to route the id per action. The remaining gap is what status values exist and whether the agent should poll, which matters given the tool's whole job is checking on in-flight work.

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?

Schema description coverage is 0%, so the description must carry the params — and it does: it disambiguates the overloaded `id`, explaining that it is the song id for 'wav' but the id returned by the upstream tool for vocals/stems/midi/voice_cover. That is meaning the schema cannot convey. The `action` enum is enumerated implicitly, but it does not say what each action's output contains.

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?

The description names the resource precisely — 'Status and file URLs of process_song / voice_cover' — so an agent knows this retrieves async results from those two specific tools. It lacks a clean leading verb ('retrieve'/'poll'), but the object and scope are unambiguous and distinguish it from siblings like get_generation.

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?

Usage is implied rather than stated: the mention of 'Status' signals this is called after/instead of a completed processing job, and the per-action id routing tells how to call it. There is no explicit when-not-to-use, no guidance on polling cadence or what to do while status is pending, and no named alternative.

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.