appagg_get_app_summaryGet a short app or game summary by AppAgg ID with a link to the full AppAgg page. Take the AppAgg ID from appagg_search_apps or appagg_new_and_deals results, or from the number at the end of an AppAgg page URL.
| Name | Required | Description | Default |
|---|---|---|---|
| appagg_id | Yes | AppAgg ID, a positive integer, for example 39642239. |
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / appagg_id / descriptionAdded value: +"AppAgg ID, a positive integer, for example 39642239."Output schema / $defs / PublicAppCard / properties / appagg_scoreAdded value: +{
+ "description": "AppAgg Score: formatted value and tier.",
+ "title": "Appagg Score",
+ "type": "string"
+}Output schema / $defs / PublicAppCard / requiredPrevious value: -[
- "appagg_id",
- "title",
- "developer",
- "platform",
- "public_url"
-]New value: +[
+ "appagg_id",
+ "title",
+ "developer",
+ "platform",
+ "public_url",
+ "appagg_score"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, non-destructive, and closed-world behavior, so the description adds rather than duplicates. It contributes meaningful context on what comes back ('a short' summary plus a link to the full page), setting expectations that this is not the full listing. It says nothing about missing/invalid IDs or link accessibility, which keeps it below a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the action and resource, then the ID provenance. Every clause carries information; nothing is redundant with the name or title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
A single required parameter with full schema coverage, an output schema for return values, and annotations for safety profile. The description supplies the one thing structured fields can't: where IDs come from and what the payload represents, which is sufficient to invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by documenting acceptable sources of the ID (search results, deals results, trailing number in an AppAgg URL), which tells the agent how to produce a valid value rather than just the type and range.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get a short app or game summary by AppAgg ID') plus the returned artifact ('a link to the full AppAgg page'). Sibling tools are named and are clearly different operations (search and deals listing vs. by-ID summary), so the agent can route without opening schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly tells the agent how to obtain the required ID: 'from appagg_search_apps or appagg_new_and_deals results, or from the number at the end of an AppAgg page URL.' That establishes when this tool is the right follow-up call. No explicit exclusions or failure cases are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.