Skip to main content
Glama

Android Developer MCP by Nova (CIVAI)

check_package_name_availability

Check whether a package name is available before creating a new app. Derived from web decompile recon, not the official API — uses the Play Console web session, not the service account.

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": {
      "developer_id": "<developer_id>",
      "package_name": "<package_name>",
      "google_account_email": "<google_account_email>"
    },
    "name": "check_package_name_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
developer_idYesNumeric Play Console developer id, from your console URL (play.google.com/console/u/N/developers/{this}/...).
package_nameYesTarget Android package name, e.g. com.example.myapp.
google_account_emailYesThe signed-in Google account email that owns this Play Console developer account. Call list_accounts first and confirm the right one with the user — do not guess.
notification_messageNoShort user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. Added
  18. Removed
  19. Added
  20. Removed
  21. Added
  22. Removed
  23. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the load and does something genuinely useful: it discloses that this is derived from web decompile recon rather than the official API, and that it rides the Play Console web session instead of the service account. That tells the agent the call is unofficial and session-dependent, which is the key risk. It does not cover failure modes, rate limits, or what an unavailable/error result looks like, so not a 5.

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, zero filler, with the purpose front-loaded and the caveat about provenance following immediately. Nothing here could be cut without losing signal.

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?

There is no output schema, so the description should say what a call returns (a boolean, an availability reason, a name-conflict detail) and what happens when the web session is stale. The auth prerequisite is covered in the schema rather than the description, which helps, but the return shape is left entirely unspecified for a check tool whose whole value is its answer.

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 developer_id, package_name, google_account_email, and notification_message are already fully documented, including the instruction to call list_accounts first and confirm with the user. The description adds no additional parameter meaning beyond the schema. Baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Check whether a package name is available') and scopes it to the pre-creation step, which implicitly distinguishes it from create_app and the other app-mutating siblings. A dedicated sibling differentiation sentence is absent, but the intent is unmistakable.

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?

The phrase 'before creating a new app' is an explicit usage trigger that tells the agent when to reach for this tool rather than calling create_app directly. There is no statement of when NOT to use it or what to do if the check is inconclusive, so it stops short of a 5.

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