Skip to main content
Glama

x402-favicon-fetch

Favicon Fetch: Builds a Google S2 favicon URL for a domain with an optional pixel size and returns the domain and url 🆓 5 free trial calls per signed wallet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-favicon-fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
sizeNo
inputNo
domainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / domain / description
      Removed value: -"Domain to process"
    • removedInput schema / properties / input / description
      Removed value: -"Input to process"
    • removedInput schema / properties / size / description
      Removed value: -"Size to process"
    • removedInput schema / properties / url / description
      Removed value: -"Url to process"
  2. Changed1 schema field changed
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "Url to process",
      +  "type": "string"
      +}
  3. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two useful behavioral facts: the underlying source (Google S2) and the payment/trial model ('5 free trial calls per signed wallet'), which implies wallet-signed auth. However it says nothing about rate limits beyond the trial, error behavior, or whether the URL is merely constructed vs. fetched.

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?

A single front-loaded sentence that leads with the action and includes the return values, with no wasted clauses. The emoji and trailing promotional quip are minor noise but do not obscure the core statement.

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 URL-builder with no output schema, the description usefully names the return values (domain and url). It is still incomplete for calling: the roles of the 'url' and 'input' parameters are never addressed, and there is no framing of the x402 wallet/payment flow beyond the trial quota.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 4 parameters, so the description must compensate. It clarifies 'domain' and an 'optional pixel size' (mapping to size), but 'url' and 'input' are left completely unexplained, and there is no indication of how url/domain/input relate to or alias one another.

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?

States a specific verb and resource: it builds a Google S2 favicon URL for a domain, with optional size, and returns domain and url. This is distinguishable from the many sibling tools, though the description never explicitly contrasts itself with nearby web/image tools like x402-gravatar-url or x402-og-image.

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?

No guidance on when to use this versus alternatives, no prerequisites, and no exclusions. The only contextual hint is the '5 free trial calls per signed wallet' note, which is a pricing constraint rather than usage guidance.

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