Skip to main content
Glama

sign_upload_parts

Idempotent

Sign at most 16 part numbers and base64 MD5 values. PUT directly to OSS, at most 3 in parallel.

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>",
      "manifest": "<manifest>"
    },
    "name": "sign_upload_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, and closed-world, and the description is consistent with that. It adds traits the annotations cannot express: the 16-part ceiling, the base64 encoding requirement for MD5, direct-PUT-to-OSS as the follow-up, and a concurrency ceiling of 3. It stops short of describing what the call returns (signed URLs?) or how long signatures remain valid.

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 filler, and the size constraint and the follow-up action are both front-loaded. Every clause carries information an agent needs to act on the result.

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 signing step with no output schema and nested manifest parts, the description covers inputs and post-call concurrency but omits the response shape, signature lifetime, and the dependency on an existing session. An agent can invoke it, but must guess at the session_id source and the return value.

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?

With 0% schema description coverage, the description must carry the load; it partly does by identifying that parts carry numbers and base64 MD5 values, clarifying encoding that the schema only implies via a 24-char length. The session_id parameter is never mentioned, and nothing says whether part numbers must be unique, contiguous, or ordered, leaving real gaps.

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?

"Sign at most 16 part numbers and base64 MD5 values" gives a specific verb (sign) and resource (upload parts) plus a hard cardinality bound, so an agent immediately knows this produces signatures for a multipart upload. It does not name or contrast with the sibling sign_upload_thumbnail, so differentiation must be inferred from the part/md5 payload.

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

Usage Guidelines3/5

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

"PUT directly to OSS, at most 3 in parallel" tells the agent what to do with the result and is genuinely actionable operational guidance. However, there is no statement of prerequisites (an open upload session from create_upload_session or get_upload_session) and no explicit when-not-to-use guidance versus siblings like sign_upload_thumbnail or resume_upload.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources