Skip to main content
Glama

TesterSwap

List an app

list_app

Add your live Google Play or App Store app from its store URL.

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": {
      "store_url": "<store_url>"
    },
    "name": "list_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
store_urlYes

Output Schema

NameRequiredDescriptionDefault
nameYes
app_idYes
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered structurally. The description adds the useful constraint that only live Google Play or App Store apps are accepted and that the input is a store URL. It says nothing about duplicate handling, what happens on an invalid URL, or what side effects follow registration (e.g., fetching metadata or tests).

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?

One short sentence with the action, the supported stores, and the input source all front-loaded. Nothing is redundant or padded.

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?

An output schema exists, so return values need not be described, and with one parameter the surface is small. However, for a mutating registration tool with no explicit mutation/permission annotation detail, the description omits prerequisites, failure behavior, and duplicate-app handling, leaving real gaps.

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 0% for the single parameter, so the description must supply meaning, and it does add that the URL must point to a Google Play or App Store listing. It does not clarify URL syntax beyond the schema's format: uri, or whether optional query strings / locale segments are tolerated.

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?

The description gives a specific verb plus resource: 'Add your live Google Play or App Store app from its store URL.' That is clearer than the name/title pair ('list_app' / 'List an app'), which misleadingly suggests enumeration rather than registration. It doesn't differentiate itself from siblings like list_my_apps, but the add-by-URL action is unambiguous within the sentence.

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?

Usage is only implied by the qualifier 'live' — the app must already be published in a store — and by the requirement to supply a store URL. There is no explicit statement of when to call this versus find_apps_to_test or list_my_apps, no mention of prerequisites, and no guidance for the case where the app is already listed.

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.