Skip to main content
Glama

Get App Store guideline by ID or section number

appstore_guideline_get
Read-onlyIdempotent

Retrieve an indexed App Store Review Guidelines section by slug or section number to get its text and source reference for guideline checks.

Instructions

Retrieve an indexed App Store Review Guidelines section by slug or section number, including its text and source reference.

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": {
      "id": "<id>"
    },
    "name": "appstore_guideline_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesGuideline anchor slug (e.g. 'safety-1-1') or section number (e.g. '1.1', '3.1.1').
formatNoResponse formatmarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.3
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.2.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the result includes text and a source reference, which is genuinely useful, but it says nothing about behavior on an invalid ID or what the format parameter changes in the response.

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 front-loaded sentence with no filler. Every clause (indexed, identifier forms, text plus source reference) carries information an agent can act on.

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 two-parameter, read-only lookup with full schema coverage and no output schema, the description adequately conveys what is returned (section text and source reference). Only error/not-found behavior and the effect of the format option are left unaddressed, which is a minor gap.

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 100%, and the schema already documents both the slug/number formats with examples and the format enum with its default. The description restates the identifier forms but adds no syntax or constraint detail beyond what the schema provides, so the baseline of 3 applies.

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 and resource ('Retrieve an indexed App Store Review Guidelines section') and specifies the two identifier forms (slug or section number). This implicitly separates it from the sibling appstore_guidelines_search, though it never names that sibling 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: 'by slug or section number' signals this is the direct-lookup path when the identifier is already known. There is no explicit statement of when to prefer this over appstore_guidelines_search or what to do if the ID is unknown.

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