DetailX Video Upscaler

sign_upload_thumbnail

Idempotent

Sign the locally extracted first-frame JPEG (at most 100 KiB / 480px). Upload it before video parts.

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": {
      "session_id": "<session_id>",
      "thumbnail": "<thumbnail>"
    },
    "name": "sign_upload_thumbnail"
  }
}

Input Schema

Name	Required	Description	Default
`thumbnail`	Yes
`session_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already cover safety (not read-only, idempotent, non-destructive), so the bar is lower. The description adds useful constraints (JPEG, <=100 KiB, 480px) but does not say what a signature returns, whether it expires, or how it ties to a session_id.

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 short sentences, front-loaded with the action and resource, with parenthetical limits and the ordering constraint appended. No wasted wording.

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?

For a two-parameter nested-object tool with no output schema, the size and format guidance is helpful but insufficient: the required md5 checksum and session binding are never explained, leaving an agent to infer them from the schema alone.

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?

Schema description coverage is 0%, so the description must compensate, and it partly does by describing the thumbnail payload's format and size limits (matching the schema's 102400 maximum and 24-char hash). However, it says nothing about md5 or session_id, so half the parameters remain unexplained.

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?

States a specific verb ('Sign') and a precise resource (the locally extracted first-frame JPEG), including format and size limits. The reference to 'video parts' hints at the sibling sign_upload_parts, though it never names it outright.

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?

Gives a concrete ordering rule: upload the signed thumbnail before video parts. That is a real sequencing guideline absent from siblings, but it does not state when the operation is optional or what to do if signing fails.

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?