Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Finish Upload

finish_upload
Idempotent

Finalizes an upload after all files are PUT to their links by verifying each file's size and activating the asset. Use cancel=true to abort and remove uploaded files instead.

Instructions

Finish an upload started with upload_asset, after every file was PUT to its link: the server checks each file's size and makes the asset ready (asset_id). Calling it again after success returns the same asset. With cancel=true it cancels instead and removes what was uploaded. If a file is missing or its size is wrong, it says so: PUT that file again (or cancel and start over if its link expired). The server keeps no operation record of this call, so operation_status can't look it up and a repeated call runs again.

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": {
      "upload_id": "<upload_id>"
    },
    "name": "finish_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
cancelNo
upload_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: states the server validates each file's size, that repeat calls after success return the same asset, that cancel removes what was uploaded, and that no operation record is kept so operation_status cannot find this call and a repeat actually re-runs. That last point is precisely the kind of caveat annotations cannot express. It is consistent with idempotentHint=true (same resulting asset) while clarifying the execution semantics.

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?

Front-loaded with the core action and its precondition, then the cancel branch, then error recovery, then the operation_status caveat. Nearly every sentence earns its place, though the stacked clauses in the first sentence make it dense and the 'it says so' phrasing is loose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 values need not be re-described; the description instead covers the gaps that matter for this two-param, network-facing completion call — validation, idempotency of the resulting asset, cancellation side effects, link expiry, and missing operation records.

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 0%, so the description carries the load: it explains cancel=true as 'cancels instead and removes what was uploaded' and ties upload_id to the flow started by upload_asset. It never explicitly defines the upload_id format or where it comes from, so it falls just short of full compensation.

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?

States a specific verb and resource and anchors it to the sibling that begins the flow: 'Finish an upload started with upload_asset, after every file was PUT to its link', then names the end result ('makes the asset ready (asset_id)'). An agent can distinguish this from upload_asset and from status-checking tools without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit preconditions (only after every file was PUT), an alternative mode (cancel=true cancels instead), and remediation branches (PUT the file again if size is wrong; cancel and restart if the link expired). When-to-use and failure handling are both spelled out.

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