Skip to main content
Glama
Sign In
Huawei App Gallery

Huawei App Gallery

by AgiMaulana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

upload_file

Upload a local file to AppGallery using a pre-signed URL to obtain a file destination URL for app file info updates.

Instructions

Upload a file to AppGallery using a pre-signed URL (Step 2 of upload flow). Returns fileDestUrl for use in update_app_file_info.

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": {
      "file_path": "<file_path>",
      "upload_url": "<upload_url>",
      "auth_code": "<auth_code>"
    },
    "name": "upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute local path to the file to upload.
upload_urlYesPre-signed upload URL from get_upload_url.
auth_codeYesAuth code from get_upload_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description must cover behavior. It indicates a mutation (upload) and states the return value, but lacks details on side effects, error conditions, or idempotency. Minimal but adequate.

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?

Single sentence, no filler, front-loaded with key action and context. Every word is necessary.

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?

Provides flow context and return value, but given no annotations or output schema, more details on failure handling, file size limits, or auth prerequisites would improve completeness. Adequate for a simple upload tool.

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 already has 100% coverage with descriptions for all three parameters. Description adds no new parameter-specific info beyond the flow context. Baseline score applies.

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?

Description clearly states it uploads a file to AppGallery via pre-signed URL, positions it as step 2 of a flow, and specifies the return value (fileDestUrl). This distinguishes it from siblings like get_upload_url (step 1) and update_app_file_info (step 3).

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?

Explicitly links to get_upload_url and update_app_file_info, implying a sequential workflow. However, it does not explicitly state when not to use or mention failure scenarios.

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