Skip to main content
Glama
Sign In
AbleSign MCP

AbleSign MCP

by MartinLoeper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

complete_media_upload

Finalize a media file upload after transferring bytes to the pre-signed URL.

Instructions

Finish an upload after bytes have been PUT to the signed upload URL.

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": "complete_media_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
upload_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must fully disclose behavior. It explains the prerequisite but omits details like idempotency, error conditions, or state changes. Adequate but minimal.

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?

One sentence with no filler. Front-loaded with the key action and condition. All words earn their place.

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?

Given the simplicity of the tool and presence of an output schema, the description provides the essential condition. Lacks details on finalization steps but is nearly complete for a single-action tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter upload_id is not described; schema coverage is 0%. The schema merely gives a title 'Upload Id', which is insufficient. The description adds no parameter guidance.

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?

Clearly states the action: 'Finish an upload after bytes have been PUT to the signed upload URL.' The verb 'finish' and resource 'upload' are specific, and the prerequisite distinguishes it from sibling tools like initiate_media_upload.

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?

Implicitly states when to use: after bytes have been PUT. Provides clear context but does not explicitly contrast with siblings like complete_media_replacement or state when not to use.

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