DetailX Video Upscaler

get_upload_instructions

Read-onlyIdempotent

Call BEFORE uploading any local video. Discover live restrictions and the automatic local upload workflow.

Codex/Claude Code with local file, shell and network access should use get_local_upload_client and these MCP control tools. The website is a fallback, not a mandatory upload step.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description adds genuinely new context: the returned restrictions are 'live' rather than static documentation, and the call is a prerequisite gate before any local video upload. It does not describe response size or how often the restrictions change, so it stops short of a 5.

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?

The critical instruction ('Call BEFORE uploading any local video') is front-loaded in the first sentence. The third sentence about Codex/Claude Code and the website being a fallback is somewhat audience-specific but still earns its place by preventing a detour to the web UI.

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 zero-parameter discovery tool with no output schema, the description covers what the call returns (live restrictions plus the automatic local upload workflow) and where it sits in the upload sequence. What is missing is a hint that the response is effectively instructions the agent must follow, rather than data to be summarized.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the schema; the baseline of 4 applies. No misleading parameter expectations are introduced.

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 states a concrete resource ('live restrictions and the automatic local upload workflow') and a concrete action ('Discover'), so an agent knows this returns upload rules rather than performing an upload. It does not explicitly distinguish itself from siblings like get_capabilities or get_upload_session, which keeps it below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call BEFORE uploading any local video' is an explicit sequencing rule, and the description routes agents with local file/shell/network access to get_local_upload_client. It also resolves the website-vs-API question by naming the website a fallback, though it gives no guidance for non-local (e.g. remote URL) uploads or when the instructions can be skipped.

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

All DetailX Video Upscaler tools Inspect

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

Need Help?