Skip to main content
Glama
Sign In
hushvert

hushvert

by hushvert
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Finish a long hushvert conversion

convert_poll

Poll a conversion job by its ID and write the completed result to a specified output path. Handles large files that need asynchronous processing.

Instructions

Resume a conversion that was still running when convert_file returned (typically a large video). Poll the job by id and, when done, write the result to output_path.

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": {
      "jobId": "<jobId>"
    },
    "name": "convert_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe job id returned by convert_file.
output_pathNoWhere to write the result once done. If omitted, returns a short-lived download URL instead.
wait_secondsNoMax seconds to wait this call. Default 120.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description must carry full burden. It mentions polling by jobId, writing result, optional output_path with download URL fallback, and wait_seconds default. However, it lacks details on error handling, rate limits, or what happens on failure.

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 sentences, no fluff, front-loaded with main action. Every word adds value.

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 polling tool with no output schema, it covers key aspects: when to use, parameters, and what happens on completion. Missing return format details when output_path omitted, but adequate overall.

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?

Schema coverage is 100% but description adds extra meaning: jobId originates from convert_file, output_path is optional with URL fallback, and wait_seconds defaults to 120. This exceeds the schema's descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Poll'/'Resume'), resource ('conversion job'), and context ('after convert_file returned for large video'), distinguishing it from siblings like convert_file that start conversions.

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?

Description explicitly says to use when a conversion is still running after convert_file returned. While it doesn't list when not to use, the context is clear enough for an agent to decide.

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

Deploy Server

Other Tools