Skip to main content
Glama

App Store Rejection Help

List common rejections

list_common_rejections
Read-onlyIdempotent

List the App Store guidelines, ITMS codes and Google Play policies this server has a plain-English guide for.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_common_rejections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and determinism are covered. The description contributes one genuinely useful behavioral fact beyond that: the list is coverage-scoped, i.e. it contains only entries the server has guides for. It does not disclose return shape, ordering, or how the returned identifiers map to the explain_* tools.

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?

A single tight sentence with no filler, and the coverage-limiting clause is placed where it matters. Every word contributes to the meaning; nothing could be removed without losing information.

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?

For a zero-parameter catalog tool with annotations and no output schema, the definition says enough to call it correctly and to understand the list is partial by design. The one missing piece is a pointer to feed returned identifiers into explain_guideline or explain_rejection, which would close the loop on the workflow.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The sentence correctly signals that no filtering or pagination inputs are expected.

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 ("List") and a clearly bounded resource: the App Store guidelines, ITMS codes and Google Play policies this server covers. The scope phrase "this server has a plain-English guide for" implicitly separates it from the explain_* siblings, which resolve one entry rather than enumerate them, though no sibling 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the discovery/catalog step before calling explain_guideline or explain_rejection. There is no explicit statement of when to call it versus the siblings, and no note that it should be used to check whether a given code is supported before attempting an explanation.

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