Skip to main content
Glama
Sign In
aso-audit-mcp

aso-audit-mcp

by ataygamesmode-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get store character limits

get_limits

Get official character limits for App Store and Google Play listing metadata to ensure your metadata stays within required lengths.

Instructions

Return the official App Store / Google Play metadata character limits. Built by asoagency.io.

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

Input Schema

NameRequiredDescriptionDefault
platformNoOmit to get both stores.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only says 'Return' – a read operation – but offers no details on authentication, rate limits, or other behaviors. For a simple read tool, minimal transparency is provided.

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?

Two sentences; the first is essential, the second ('Built by asoagency.io') is non-functional branding. Nearly concise with minimal waste.

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 this simple tool with one optional parameter and no output schema, the description sufficiently states what is returned. No additional details are needed for the agent to use it correctly.

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%, so description adds no extra meaning. The schema already describes the optional platform parameter and its default behavior (omit for both). Description does not enhance beyond baseline.

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 clearly states the tool returns App Store and Google Play metadata character limits, using a specific verb and resource. It naturally distinguishes from sibling tools (e.g., audit_metadata) which focus on other aspects.

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?

The description implies usage when character limits are needed, but provides no explicit when-to-use, when-not-to-use, or alternative tools. Without guidance, the agent may not differentiate from siblings.

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