Skip to main content
Glama
Sign In

DubSync

by me.dubsync
OverviewDiscussionsAdmin

Get translated media

dub_get_project_result
Read-onlyIdempotent

Use after a project completes to retrieve its result and available downloads. Download URLs expire; do not publish private result links.

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": {
      "projectId": "<projectId>"
    },
    "name": "dub_get_project_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Output Schema

NameRequiredDescriptionDefault
dataYesThe safe public API response, or resumable-upload status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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), so the description's value-add is the operational warnings: download URLs expire and result links are private and must not be published. That is genuine behavior an agent could not infer elsewhere. It stops short of saying what happens if the project is not yet complete (error vs. partial result).

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 with no waste; the usage precondition comes first and the caveats follow. Nothing is redundant with the schema or annotations.

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?

An output schema exists, so return contents need not be described, and the description covers the caller-facing risks (expiry, privacy). The remaining gap is the not-yet-complete behavior of the call, which matters given the tool's lifecycle framing.

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?

One required parameter with 0% schema description coverage, so the description carries the burden. 'Its result' implies the identifier selects the project whose result is returned, but the description never states that the parameter is a project ID or what accepted identifier forms are (the schema's pattern hints at prefixed IDs but is not self-explanatory).

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 and resource ('retrieve its result and available downloads') and anchors it to the project lifecycle ('after a project completes'), which separates it from dub_get_project_status (checks progress) and dub_get_project (metadata). The word 'result' is somewhat abstract, but 'available downloads' concretizes the payload.

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 an explicit timing prerequisite: only use after a project completes. It does not name dub_get_project_status as the way to confirm completion, leaving the sequencing half-implied, and no exclusion for in-progress projects is stated.

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

All DubSync toolsInspect
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