Skip to main content
Glama
Sign In
Huawei App Gallery

Huawei App Gallery

by AgiMaulana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_app_file_info

Attach uploaded files to an app draft by providing file type, names, destination URLs, and SHA256 checksums.

Instructions

Attach already-uploaded files to the app draft. Use after get_upload_url + manual upload.

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_type": "<file_type>",
      "files": "<files>"
    },
    "name": "update_app_file_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idNoAppGallery Connect app ID. Optional if HUAWEI_APP_ID is set in the environment.
file_typeYes1=APK, 2=RPK, 5=AAB.
filesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, and the description only says 'Attach' without disclosing behavioral traits like side effects, idempotency, or permissions. Minimal transparency.

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 short sentences with no filler; the first states purpose, the second provides usage context. Highly concise.

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?

Minimal but covers the core action. Lacks details on return values, error handling, or behavior after attachment. Adequate for a simple tool with no output schema.

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?

Schema coverage is 67%, and the description adds no extra meaning beyond the schema. For example, it doesn't explain how 'files' are attached or the role of 'file_dest_url'.

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?

The description clearly states the verb 'Attach' and the resource 'already-uploaded files to the app draft', distinguishing it from siblings like upload_app_file which uploads files.

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 says 'Use after get_upload_url + manual upload', providing a clear usage sequence. No alternatives or exclusions, but the context is sufficient.

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