app-store-version

app_store_version

app_store_version

Checks current App Store version by bundle ID. x402 payment required (testnet USDC).

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": {
      "bundleIds": "<bundleIds>"
    },
    "name": "app_store_version"
  }
}

Input Schema

Name	Required	Description
`country`	No	国コード(既定us)
`payment`	No	x402 payment payload (base64 JSON), signed EIP-712 exact/transferWithAuthorization. Omit on the first call — the tool will return payment requirements (accepts[]) as an error result.
`maxItems`	No
`bundleIds`	Yes	App StoreのbundleId配列

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The description discloses the unusual payment requirement but doesn't explain that the first call is expected to fail and return payment requirements as an error result. Since annotations are absent, the description carries the full behavioral disclosure burden and only partially meets it.

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 concise sentences with no filler. The core function and the most important constraint (payment) are front-loaded. Every word earns its place.

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?

The tool's purpose and payment requirement are clear, but the two-step payment handshake is not spelled out in the description. The country and maxItems parameters are only minimally described in the schema, and the description doesn't compensate. Still, the core operation is adequately covered.

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

Parameters4/5

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

Schema coverage is 75%, and the payment parameter is well documented with the two-step behavior. The description adds value by clarifying the payment currency (testnet USDC) and framing the tool's purpose around App Store version checking.

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 states a specific action ('Checks current App Store version') and a specific input mechanism (bundle ID). It doesn't name sibling tools to differentiate from, but no siblings are listed, so the clarity is sufficient for selection.

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 includes practical usage context by noting 'x402 payment required (testnet USDC)'. However, it doesn't explicitly describe the two-step payment flow (omit payment first, then receive requirements and retry), which is only implied by the schema's payment parameter description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All app-store-version tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?