Skip to main content
Glama

550W AI去字幕去水印

get_media_capabilities

Read-onlyIdempotent

Discover regional business capabilities, action scopes and input limits; this does not grant access.

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_media_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds a genuinely non-obvious clarification — that discovering scopes and limits does not itself authorize any operation — which prevents an agent from assuming discovery implies permission. It stops short of saying whether results vary by credential or how limits are scoped.

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?

A single compact sentence, front-loaded with the verb and the payload enumeration, with the access caveat attached at the end where it belongs. No filler, though the semicolon-joined caveat and the vague 'regional business capabilities' phrase slightly reduce crispness.

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?

With no parameters and no output schema, the description carries the burden of conveying what comes back; it names three categories of return data but gives no sense of structure, keys, or how limits are expressed. Adequate to prompt a call, insufficient to tell an agent what the response will look like or how to consume it.

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?

Zero parameters with an empty object schema and additionalProperties=false, so there is nothing for the description to disambiguate; baseline 4 applies. The phrase 'input limits' could be misread as a parameter concern, but here it clearly refers to returned metadata.

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 uses a concrete verb ('Discover') and enumerates the resource set returned: regional business capabilities, action scopes, and input limits. That distinguishes it from every sibling, which are all task-execution or credit-query tools, though 'regional business capabilities' remains abstract phrasing that an agent must interpret.

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?

Nothing states when to call this versus alternatives, or that it should be consulted before submit_media_task / prepare_media_upload to learn accepted limits. The caveat 'this does not grant access' is a behavioral note, not usage guidance, so selection must be inferred from the purpose statement 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