Skip to main content
Glama

App Store Rejection Help

Explain one guideline or policy

explain_guideline
Read-onlyIdempotent

Explain a single App Store Review Guideline (e.g. "4.2", "2.5.19", "5.1.1(v)"), an ITMS upload error ("ITMS-91053") or a Google Play policy name ("Data safety section"). Use it when there is no full rejection message.

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": {
      "reference": "<reference>"
    },
    "name": "explain_guideline"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceYesOne guideline number, ITMS code or Play policy name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 the safe-lookup profile is fully covered by structured data. The description adds nothing beyond that profile — no note on what happens with an unrecognized reference, no indication of lookup source or staleness, and no hint at the shape of the explanation returned. Creditable but thin given annotations carry the behavioral load.

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 sentences: the first defines the accepted input space with examples, the second states the selection condition. No filler, no restatement of the title, and the most decision-relevant information (what counts as a valid reference) comes first.

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 one-parameter lookup with no output schema and strong annotations, the description covers what an agent needs in order to call it correctly. The minor gap is that it says nothing about the returned explanation or behavior on an unknown reference, which is the one uncertainty an agent would still have.

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 genuinely enriches the single parameter by enumerating three distinct reference families and giving literal example strings for each ("2.5.19", "5.1.1(v)", "Data safety section"). That materially reduces the chance of an agent passing a malformed or free-text reference.

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 names a specific verb ("Explain") and a precisely bounded resource: a single guideline number, ITMS error code, or Play policy name, with concrete format examples ("4.2", "ITMS-91053"). It separates itself from a rejection-message tool via the "single" scope and the no-full-message condition, though it never names the sibling it is distinguished from.

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?

"Use it when there is no full rejection message" gives an explicit entry condition and implicitly carves out the case handled by explain_rejection. It stops short of naming that alternative or stating what to do if a full rejection message does exist, so the routing is inferable rather than spelled out.

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