Skip to main content
Glama

DomainVet

Find a site's favicon and icons

favicon_find
Read-onlyIdempotent

Find a website's icons: <link rel=icon / apple-touch-icon / mask-icon> with sizes and types, the default /favicon.ico (verified), the og:image, and the best icon URL to display.

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": {
      "url": "<url>"
    },
    "name": "favicon_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesSite URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safe read-only, idempotent, open-world profile, but the description adds real behavior: it fetches and parses link tags, explicitly verifies the default /favicon.ico, and computes a best icon URL for display. It does not state fallback behavior when nothing is found or whether redirects/schemes are handled, leaving a small gap.

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 packs the discovery sources, the verification step, and the display-ready output in order of importance, with no filler or repetition.

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 one-parameter read tool with no output schema, the description effectively doubles as a return-value summary by listing every icon source and the best-URL result. Only edge-case behavior (no icons found, fetch failures) is left unaddressed.

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?

With one parameter at 100% schema coverage, the schema already defines "Site URL." The description only implies the URL should be the site's address, adding no syntax, scheme, or path-level detail beyond the schema, so the baseline 3 applies.

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?

Uses a specific verb ("Find") against a specific resource (a site's icons) and enumerates exactly what it collects: rel=icon, apple-touch-icon, mask-icon with sizes/types, the default /favicon.ico, og:image, and a best icon URL. No sibling (dns_lookup, security_headers, sitemap_urls, etc.) overlaps this scope, so an agent can route to it unambiguously.

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 purpose implies when to use it — retrieving a site's icon assets — but there is no explicit when/when-not guidance, no prerequisites about the URL format, and no mention of what to do if no icons exist. Usage is inferable rather than stated.

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