Skip to main content
Glama

Consultar resumen de Google Play

estado_play_store
Read-onlyIdempotent

Resumen de comparación con exportaciones autorizadas de Google Play, nunca verificación en tiempo real.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely non-obvious trait beyond them: the data comes from authorized exports and is never real-time, which is a meaningful staleness caveat an agent cannot infer from annotations. It stops short of describing what the comparison output looks like.

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?

A single sentence with no filler, and the most decision-relevant clause (never real-time) is present rather than buried. It is efficient, though its brevity contributes to the missing purpose detail rather than reflecting genuine completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description is the only source of information about what an agent receives, and it does not say what the summary covers or what is compared. The freshness caveat is valuable, but for a zero-arg reporting tool the definition should say more about the scope of the returned summary.

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 zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. Schema coverage is 100% and additionalProperties is false, leaving no ambiguity to compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it is a 'resumen de comparación' against authorized Google Play exports, which identifies the resource loosely, but it never states what is being compared (apps, catalog, metadata) or what the summary contains. It largely restates the title 'Consultar resumen de Google Play' with a caveat attached, so the purpose stays vague.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no sibling is named as an alternative. The only directional hint is the implied exclusion 'nunca verificación en tiempo real', which tells an agent not to rely on it for live checks but does not route it to any other tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.