Skip to main content
Glama

550W AI去字幕去水印

quote_media_task

Read-only

Verify a quote for a server-uploaded video mediaId. No charge; not a balance reservation.

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": {
      "mediaId": "<mediaId>"
    },
    "name": "quote_media_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
modeNo
mediaIdYes
fileNameNo
removeAudioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description still earns credit by disclosing billing semantics that no annotation conveys: 'No charge; not a balance reservation' tells the agent that calling this will not consume credits, which matters for a quote tool that looks like it might. It stops short of saying whether the quote expires, is repeatable, or what it returns.

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?

Two short sentences, front-loaded with the core action, and no wasted words. It is tight to the point of under-specification, but that is a completeness problem rather than a conciseness one.

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

Completeness2/5

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

For a tool with five parameters, one enum, zero schema documentation and no output schema, the description is far too thin — an agent cannot tell what mode or area do or what a returned quote contains. The only genuinely informative content is the billing clarification.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 5 parameters, so the description must carry the meaning of area, mode (normal/protect enum), fileName, and removeAudio — and it explains none of them. Only mediaId is hinted at, and even that adds just the 'video' constraint. Four of five parameters remain opaque.

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?

States a verb (verify) and resource (a quote for a video mediaId), so the general intent is graspable, but 'verify a quote' is ambiguous — it never says a quote is a price/cost estimate for a subsequent processing job. Nothing distinguishes it from the sibling estimate_subtitle_cost, which plausibly does a similar quoting job.

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?

The phrase 'server-uploaded video mediaId' implies a prerequisite (the media must already be uploaded via prepare_media_upload / prepare_verified_video_upload), which is useful implied usage. But there is no explicit when-to-use rule, no statement of how this relates to submit_media_task, and no guidance on whether the quote must precede submission.

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