Skip to main content
Glama

Obtener ficha de aplicacion

obtener_app
Read-onlyIdempotent

Obtener ficha de aplicación mediante paquete Android o slug exacto.

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": {
      "identificador": "<identificador>"
    },
    "name": "obtener_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
identificadorYesID de paquete Android o slug exacto de una aplicacion del catalogo publico.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / identificador / description
      Added value: +"ID de paquete Android o slug exacto de una aplicacion del catalogo publico."
  2. 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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the fact that matching is exact against a package/slug; it says nothing about behavior on a miss (error vs empty) or that lookup is limited to catalog entries.

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?

One short front-loaded sentence with no filler. It is efficient, though the brevity leaves gaps that a second clause could have closed.

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

Completeness2/5

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

The tool is simple and well-annotated, but there is no output schema and the description never indicates what the 'ficha' contains or what happens when the identifier is unknown. For a retrieval tool with no documented return shape, that leaves the agent guessing.

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 description coverage is 100% and the single parameter already documents 'ID de paquete Android o slug exacto'. The description restates the same constraint without adding format examples, case sensitivity, or ambiguity handling, so 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 names a specific verb and resource ('Obtener ficha de aplicación') and states the two accepted lookup keys (Android package or exact slug). This distinguishes it implicitly from search-oriented siblings like buscar_apps, though it never names them.

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 or when-not-to-use guidance, and no alternatives are named. The word 'exacto' hints that this is an exact-match retrieval rather than a search, but the agent must infer that from a single adjective.

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.