Skip to main content
Glama
Sign In
Huawei App Gallery

Huawei App Gallery

by AgiMaulana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_gms_dependency

Declare if your app requires Google Mobile Services (GMS) by setting a flag, ensuring correct dependency configuration for AppGallery publishing.

Instructions

Declare whether the app depends on GMS (Google Mobile Services).

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": {
      "need_gms": "<need_gms>"
    },
    "name": "set_gms_dependency"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idNoAppGallery Connect app ID. Optional if HUAWEI_APP_ID is set in the environment.
need_gmsYes0=no GMS, 1=requires GMS.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses the action (declare dependency) but omits side effects, authorization needs, or validation behavior. For a simple setter, this is adequate but not thorough.

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?

The description is a single, concise sentence with no superfluous information. Every word earns its place.

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?

Given no output schema and simple parameters, the description adequately covers the tool's purpose. It could optionally mention the optional app_id, but the schema already handles that.

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?

Input schema has 100% description coverage for both parameters. The description does not add significant meaning beyond the schema, so baseline score of 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?

The description uses a specific verb ('declare') and resource ('GMS dependency'), clearly stating the tool's function. It distinguishes itself from siblings, which involve app submission, uploads, and reports, making its purpose unique.

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?

The description does not explicitly state when to use or not use this tool, nor does it mention alternatives. However, the context implies it is used for setting GMS dependency, which is a specific action with no clear competing sibling.

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