All SVG Icons

Find brand logo

find_brand_logo

Read-only

Finds a company, product, or technology logo by name or domain. Use this when the user asks to find a logo. Returns matching icons in "prefix:name" format with their style (color, mono, wordmark) and, when available, a brand hex color. Get the SVG of a result with get_icon. Where supported, it also displays the color and an icon grid.

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": {
      "brand": "<brand>"
    },
    "name": "find_brand_logo"
  }
}

Input Schema

Name	Required	Description	Default
`brand`	Yes	Company, product, or technology name, or a domain such as "example.com"

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / brand / description

Previous value: -"Brand name or domain, e.g. \"GitHub\" or \"github.com\""New value: +"Company, product, or technology name, or a domain such as \"example.com\""

AddedOct 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/non-destructive, so the description's real contribution is the return shape ('prefix:name', style variants, optional brand hex color) and the note that it may render a color and icon grid where supported. That is useful context beyond annotations, though no-match or empty-result behavior is left unstated.

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 purpose, then usage, then return format and the handoff to get_icon — a sensible order. The trailing sentence about displaying a color and icon grid is slightly incidental but still short.

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?

With no output schema, the description correctly spends its words explaining the return value format and the get_icon follow-up, which is what an agent needs. Only edge cases (no results, ambiguous brand names) are absent.

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 the single 'brand' parameter is fully documented there. The description's 'by name or domain' merely restates the schema, adding no syntax or format detail beyond it.

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 ('Finds a company, product, or technology logo') and scopes it to brand/domain input, which separates it from search_icons and list_collections. An agent can identify the tool's remit without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this when the user asks to find a logo' and then routes the follow-up step to get_icon for the SVG. It gives clear positive guidance but never states exclusions or when to prefer search_icons instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All All SVG Icons tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?