Skip to main content
Glama
Sign In
iran-apps-mcp

iran-apps-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

App details

ap_app
Read-onlyIdempotent

Retrieve one app's metadata from Cafe Bazaar or Myket—version, rating, installs, size, price, developer, and update date—to inspect a single Android package.

Instructions

Get one app's metadata from one store: version, rating and rating count, installs, size, update date, developer, price, description.

Bazaar also gives version_code, a 1-5 star histogram, changelog and permission count; Myket also the first publish date and developer_id. Prices are Toman, 0 = free. For both stores at once use ap_compare.

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": {
      "package": "<package>"
    },
    "name": "ap_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeNo'bazaar' or 'myket'.bazaar
packageYesAndroid package name, e.g. 'com.whatsapp'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / package / description
      Previous value: -"Android package name, the id in store URLs, e.g. 'ir.mci.ecareapp' or 'com.whatsapp'."New value: +"Android package name, e.g. 'com.whatsapp'."
    • changedInput schema / properties / store / description
      Previous value: -"'bazaar' (Cafe Bazaar) or 'myket'."New value: +"'bazaar' or 'myket'."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds real substance beyond that: which fields each store returns, that Bazaar's extra fields include version_code, histogram, changelog and permission count, and that prices are in Toman with 0 meaning free. Only the shape/format of the response (flat object vs nested) is left implicit.

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

Conciseness4/5

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

Front-loaded with the core action, then store-specific deltas, then a routing pointer. The store-specific sentences are dense but each carries field-level information an agent would otherwise have to discover empirically; minor redundancy in re-listing the base fields twice.

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?

With no output schema, the description carries the burden of describing returns and does so field by field, including store-specific extras and price units. Complete enough to call correctly and interpret results; only the structural form of the response is unspecified.

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 100%, so the baseline is 3, but the description earns more by explaining what the store parameter actually buys you: bazaar yields version_code, star histogram, changelog and permission count, while myket yields first publish date and developer_id. That is decision-relevant meaning the enum labels do not provide.

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?

States a specific verb and resource ('Get one app's metadata from one store') and enumerates the returned attributes (version, rating, installs, size, developer, price). The 'one store' scope immediately distinguishes it from ap_compare, which is named explicitly.

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?

Gives a clear routing rule: use this for a single store, use ap_compare for both stores at once. No explicit exclusion for ap_search or ap_similar, but the single-app scope makes the boundary reasonably clear from context.

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