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

app-store-connect

by RayanBayat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

maintenance_confirm_review

Records the user's explicit confirmation after they review a maintenance report. Nothing is saved without their yes; use only after showing the report.

Instructions

Record that the user read the maintenance report. The user is asked to confirm in a form; nothing is recorded without their explicit yes. Call this only after showing the user the report from maintenance_report.

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": {
      "summary": "<summary>"
    },
    "name": "maintenance_confirm_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
summaryYesOne or two sentences: what changed and what was decided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses the consent gate: nothing is recorded without the user's explicit yes, and a form confirmation is involved. It does not explain what a repeat call does, even though idempotentHint is false, leaving the duplicate-call consequence unstated.

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?

Three short sentences, front-loaded with the action and followed by the consent constraint and the ordering rule. Nothing is padding, though the consent sentence is mildly restated between its two clauses.

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 single-parameter write tool with full schema coverage and no output schema, the description covers purpose, consent semantics, and call ordering. The only meaningful omission is what a non-idempotent repeat call produces, which the agent would need to avoid duplicates.

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 coverage is 100% and the single 'summary' parameter already carries its own description, so the schema does the heavy lifting. The tool description adds no guidance on what the summary should contain (e.g., that it must reflect the report the user just saw), so the baseline 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 states a specific verb and resource: record that the user read the maintenance report. That reads clearly as a confirmation-recording action distinct from maintenance_report and maintenance_status, though it never explicitly names those siblings as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives an explicit precondition: 'Call this only after showing the user the report from maintenance_report,' which both orders the call correctly and names the sibling that must run first. An agent knows exactly when this becomes callable and what gates 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