Skip to main content
Glama
Sign In
App Store Publisher MCP

App Store Publisher MCP

by qalvinahmad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

huawei_api_request

Send HTTP requests to Huawei AppGallery API for app publishing, updates, and submissions.

Instructions

Alias of appgallery_api_request (kept from the old huawei-appgallery-connect MCP)

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": {
      "method": "<method>",
      "endpoint": "<endpoint>"
    },
    "name": "huawei_api_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNo
methodYes
paramsNo
endpointYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations provided. The description does not disclose any behavioral traits: no mention of authentication requirements, side effects, error handling, or rate limits. The alias reference implies behavior but doesn't specify it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (one sentence), but it fails to convey essential information. It does not earn its place because it omits critical details about tool behavior and usage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (4 parameters, no annotations, no output schema), the description is completely inadequate. It should explain the tool's purpose as a raw HTTP client, authentication context, and parameter roles.

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

Parameters1/5

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

Schema description coverage is 0%. The description adds no meaning to the four parameters (method, endpoint, data, params). It doesn't explain expected format, constraints, or how parameters interact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool is an alias of appgallery_api_request, but does not explain what it does (e.g., 'make direct API calls to Huawei AppGallery'). The purpose is vague and relies on knowledge of the aliased tool.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus siblings like appgallery_api_request, huawei_public_api_request, etc. The description lacks any context for selection.

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