Skip to main content
Glama

Get the best favicon/icon for a website

favicon
Read-only

Get the best favicon/icon for a website: the largest declared icon (apple-touch-icon, SVG, sized PNGs), all candidates with sizes, and whether /favicon.ico exists. Fast (under 2 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.001 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declared, the description adds meaningful non-schema context: expected latency (under 2 s), a concrete free quota (20 calls/day per user across free tools), and the overage price and payment rail. It does not explain failure behavior when payment is missing or how candidate ranking breaks ties, so it stops short of fully transparent.

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?

Front-loaded with the capability and the return contents, then the operational constraints. It is dense but nearly every clause carries information; the pricing sentence is long yet justified for a paid tool, though the enumeration of icon types sits close to redundancy with the title.

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?

No output schema exists, so the description must describe results, which it does at a useful level (best icon, candidate list with sizes, favicon.ico presence). Payment mechanics are fully delegated to the schema, leaving only minor gaps around error or unpaid-response behavior.

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 description coverage is 100%, including a detailed explanation of the x402 payment parameter and the omit-on-first-call pattern. The description adds no meaning beyond the schema for either the url or payment parameters, 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?

States a specific verb and resource ("Get the best favicon/icon for a website") and immediately specifies what comes back: the largest declared icon types, all candidates with sizes, and whether /favicon.ico exists. This clearly separates it from siblings like og_image, images, or screenshot, which serve different retrieval purposes.

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 implied by the stated return contents – an agent can infer this is the tool for resolving site icons rather than listing images. However, there is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as the alternative for related needs such as fetching a social preview image.

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.