Skip to main content
Glama

Find a site's icons, og:image and theme colour

logo
Read-only

A site's brand assets: its icons (favicon, apple-touch-icon and web app manifest icons, largest first), the og:image, theme colour and site name, read from the page and its manifest. Falls back to /favicon.ico when the page declares no icon. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
urlNoSite address, https://… (or give domain)
domainNoDomain name, e.g. stripe.com

Output Schema

NameRequiredDescriptionDefault
siteNo
iconsNo
sourceNo
ogImageNo
siteNameNo
checkedAtNo
themeColorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name, e.g. www.python.org"New value: +"Domain name, e.g. stripe.com"
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description adds real value beyond them: icon ordering, the /favicon.ico fallback, and the billing model ($0.002 per successful call via x402, failed calls not charged) which matters for an agent deciding to retry. It stops short of describing rate limits or how partial failures (e.g. manifest unreachable) are reported.

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-loads the asset list, then the fallback, then pricing, with no filler sentences. Only minor drag from packing the payment-network detail ('USDC on Base, Solana and 10 more networks') into the same breath as the core behavior.

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?

An output schema exists so return shape need not be explained, and the description covers source (page and manifest), ordering, fallback, and cost. The one gap is guidance on url vs domain usage, which is not fully resolved by the schema.

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%, so both parameters (url and domain) are already documented in the input schema, establishing the 3 baseline. The description adds nothing about whether url and domain are alternatives or whether both may be supplied, despite zero required parameters.

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 pair ('A site's brand assets: its icons... og:image, theme colour and site name') and enumerates exactly which assets are returned, including precedence (largest first) and the /favicon.ico fallback. An agent can tell immediately this is the brand-asset extraction tool rather than a generic page reader.

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 fallback behavior ('Falls back to /favicon.ico when the page declares no icon') implies the extraction works on any page, but there is no explicit when-to-use or when-not-to-use guidance, nor routing to a sibling such as 'image' or 'read'. Usage is only inferable from the purpose.

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