Skip to main content
Glama
Sign In
home-screen-mcp

home-screen-mcp

by worldsavepoint
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_icons

Fetch icon images for up to 24 app IDs in the order provided, so you can match apps to their Home Screen icons during layout review.

Instructions

Icon images for up to 24 apps, in the order given.

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": {
      "ids": "<ids>"
    },
    "name": "get_icons"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the 24-app cap and ordering semantics, but omits the return format (URLs, base64, etc.), error behavior above the limit, and any permission requirements—significant gaps for a tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single front-loaded sentence that states the resource, the batch cap, and the ordering rule with zero filler.

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 simple one-parameter tool with no output schema, the description is only partially complete. It identifies the return as 'icon images' but does not say in what form they come back or how the 24-item limit is enforced.

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 0%, so the description must compensate. It adds that the array is capped at 24 and that order is preserved, which is meaningful beyond the bare schema, but it never clarifies what the 'ids' strings represent (app identifiers, bundle IDs, names).

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 states a specific resource (icon images) and scope (up to 24 apps, in the order given), so an agent can tell what it returns. It does not differentiate from siblings like icon_colors, which could be confused with it.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. Usage is only implied by 'Icon images for up to 24 apps'.

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