Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_media_favicon_hd_resolver

Resolve a domain's published icon dimensions and choose the larger-dimension version across SVG, Apple touch, Android, and favicon formats instead of a default favicon.

Instructions

[Dynamic Media] Find the highest-resolution icon a domain publishes (SVG, apple-touch, Android, favicon) with dimensions Measured p50 12 ms, p95 42 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://media.caelaralabs.com.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two genuinely useful behavioral facts that structured data does not: the tool calls an external service at https://media.caelaralabs.com and typical latency (p50 12 ms, p95 42 ms). It does not say what happens when a domain publishes no icon, whether the lookup hits the live domain or a cache, or how failures surface.

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?

The core capability is front-loaded in the first clause and the format list follows immediately, so nothing important is buried. The benchmark citation and endpoint are dense but defensible; the bracketed '[Dynamic Media]' prefix and abbreviated 'with dimensions' phrasing add slight noise.

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 one required parameter, no annotations, and no output schema, the definition covers the basics but leaves return shape underspecified: 'with dimensions' hints at metadata but the agent cannot tell what fields come back or what an empty result looks like. For a network-backed resolver, a sentence on the no-icon case would close the main gap.

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 there is only one parameter, already documented with an example ('github.com'), so the description need not repeat it. The phrase 'a domain publishes' adds only marginal meaning beyond the schema and does not clarify accepted input variants such as full URLs with paths or subdomains.

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 uses a specific verb ('Find') on a specific resource ('the highest-resolution icon a domain publishes') and enumerates the candidate formats (SVG, apple-touch, Android, favicon), so an agent knows exactly what comes back. It stops short of naming a sibling it should be preferred over, so differentiation from tools like image_meta_inspector is left to inference.

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 when-to-use or when-not-to-use statement, no prerequisite, and no named alternative among the media siblings. The agent must infer from the purpose line alone that this is the tool for pulling a site's icon, and cannot tell whether it should use this versus the image-meta or social-card tools.

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