Skip to main content
Glama

obtener icono app

obtener_icono_app
Read-onlyIdempotent

Obtiene y devuelve la imagen PNG oficial de una aplicación AppInitDev, sin usar imágenes alternativas.

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_icono_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
identificadorYesPaquete Android o slug exacto de la aplicación cuyo ícono oficial se solicita.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the bar is lower. The description still adds real behavior beyond them: the return is an official PNG image and no substitute/placeholder image is supplied, which tells the agent failure means no icon rather than a fallback. It does not describe the exact payload shape, which keeps it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the verb and resource first and the 'no alternative images' caveat second; nothing is redundant. The branding/qualifier phrasing ('AppInitDev', 'oficial') is slightly padded but harmless.

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?

For a one-parameter read tool with annotations and full schema coverage, the definition covers purpose and the key fallback behavior. With no output schema, though, it leaves the response form vague (image content block vs. URL or base64) and says nothing about the failure case when no official icon exists.

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 parameter is already documented as an Android package or exact slug, so the schema carries the meaning. The description only reinforces that the identifier selects an AppInitDev app, adding no format, casing, or validation detail beyond the schema. 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?

States a specific verb pair and resource: 'Obtiene y devuelve la imagen PNG oficial de una aplicación'. The agent can tell this returns an image asset rather than app metadata, implicitly separating it from obtener_app. It does not name any sibling explicitly, so it stops short of a 5.

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?

Usage is only implied: fetch this when you need the icon file itself. There is no explicit statement of when to prefer it over obtener_app, nor any note about what to do if the icon is unavailable. The 'sin usar imágenes alternativas' clause hints at a constraint but does not frame it as guidance.

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.