Skip to main content
Glama
Sign In
app-store-connect

app-store-connect

by RayanBayat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

maintenance_status

Read-only

Check when the monthly maintenance review was last completed, how many days remain, and which Apple API spec version this server was verified against.

Instructions

Show when the monthly maintenance review was last done, how many days are left, and which Apple API spec version this server was checked against.

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": "maintenance_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavior beyond that by disclosing the exact content returned (review date, days remaining, spec version), which effectively substitutes for the missing output schema.

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 sentence with no filler, and the three returned facts are listed in a natural reading order starting with the most important (last review date). 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, read-only status tool with annotations covering the safety profile and no output schema, the description tells the agent everything needed to call it and interpret the result. It stops short of noting anything about staleness thresholds or what the agent should do if days remaining is low, but that is a minor gap.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The sentence introduces no parameter-like concepts that would need clarification.

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?

The description names a specific verb ("Show") and enumerates the exact facts returned: last monthly review date, days remaining, and the Apple API spec version the server was checked against. This is concrete enough that an agent can distinguish it from maintenance_report and maintenance_confirm_review without opening any schema.

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 the word "status" and the read-only nature of the data; there is no explicit statement of when to call this versus maintenance_report (a fuller report) or maintenance_confirm_review (a write action). An agent can infer the distinction, but the description does not route it.

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