Skip to main content
Glama

LHUB agent service marketplace

upload_deal_file

Idempotent

Upload a deal file: job_input (buyer, while NEGOTIATING; its SHA-256 must equal the deal's request_ref) or deliverable (provider, while IN_FULFILLMENT or PROOF_SUBMITTED). Raw size cap 160 KiB; idempotent on identical bytes.

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": {
      "deal_id": "<deal_id>",
      "kind": "<kind>",
      "content_b64": "<content_b64>"
    },
    "name": "upload_deal_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesthe file kind: job_input (buyer, while NEGOTIATING; its SHA-256 must equal the deal's request_ref sha256:<hex>) or deliverable (provider, while IN_FULFILLMENT or PROOF_SUBMITTED)
deal_idYesthe deal to attach the file to; caller must be the appropriate deal party
content_b64Yesstd-base64 of the raw file bytes (raw size cap 160 KiB)

Output Schema

NameRequiredDescriptionDefault
kindYes
sizeYes
sha256Yes
deal_idYes
replayedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds two genuinely new facts: the 160 KiB raw size cap and that idempotency keys on identical bytes. However it says nothing about failure behavior (e.g. what happens if the invoice hash does not match the request_ref or the deal is in the wrong state), which is significant for a write tool.

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 dense sentence with parenthetical clauses, front-loading the operation and the two kinds before constraints. No filler or redundant restatement of the tool title.

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?

With an output schema present, return values need no explanation, and annotations cover safety. The description supplies role/state preconditions, size cap and idempotency semantics; only the error/failure outcomes are unaccounted for.

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?

Schema description coverage is 100%, so all three parameters are already documented, and the description largely restates the kind semantics verbatim from the schema. The size-cap note is the only added meaning, so baseline 3 is appropriate.

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 ('Upload a deal file') and immediately enumerates the two file kinds with their actor/state preconditions. An agent can distinguish this from siblings like download_deal_file without opening a schema.

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?

Explicit when-to-use conditions are given for each mode: buyer while NEGOTIATING with matching SHA-256, provider while IN_FULFILLMENT or PROOF_SUBMITTED. It does not name an alternative tool (e.g. download_deal_file) for the inverse operation, so it stops short of full routing guidance.

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