Skip to main content
Glama

Caelara Labs Dynamic Media

favicon_hd_resolver

Find the highest-resolution icon a domain publishes (SVG, apple-touch, Android, favicon) with dimensions

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": {
      "domain": "<domain>"
    },
    "name": "favicon_hd_resolver"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain or URL, e.g. github.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does add some value by disclosing the candidate sources and that the resolver picks the highest-resolution option and reports dimensions, which implies a read-only network fetch. It omits failure behavior when no icon exists, whether requests leave the sandbox, and any rate-limit or caching behavior, which matters for an unannotated tool.

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?

One front-loaded sentence with zero filler: the verb, the selection rule, the candidate formats, and the returned dimensions all appear in order of importance. Nothing is repeated from the name or schema unnecessarily.

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 a low-complexity, single-parameter lookup with a fully described schema and no output schema, the description covers what the tool returns ('with dimensions') and how it chooses. The remaining gap is failure/empty-result behavior, which is a modest omission rather than a blocking one.

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 already documents 'Domain or URL, e.g. github.com', so the description adds little beyond the schema. It does implicitly confirm that only a domain is needed rather than a full icon URL, but gives no detail on URL normalization or scheme handling. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names a specific verb ('Find') and a precise resource ('the highest-resolution icon a domain publishes'), enumerating the format sources (SVG, apple-touch, Android, favicon) and noting that dimensions are returned. Against a sibling set of generators and composers (badge_shield_generator, qr_code_svg_builder, brand_kit_composite), it is unambiguous that this tool performs a read/lookup rather than producing an asset.

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 usage context is implied by the phrase 'a domain publishes' and by the 'highest-resolution' selection criterion, so an agent can infer it is for discovering an existing icon rather than generating one. However, there is no explicit statement of when to prefer it over a sibling, no mention of whether a live network fetch of the domain is performed, and no guidance on what to do if the domain publishes no icon.

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.

Resources