Skip to main content
Glama

Find logos

find_logos
Read-only

Look up logos for domains or product names. Returns, per query: found/fallback, confidence (0 = placeholder), name, source URL and size, and public PNG/WebP/ICO/SVG URLs.

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": {
      "queries": "<queries>"
    },
    "name": "find_logos"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesDomains (stripe.com) or product names (Microsoft Entra ID, CoCounsel). Up to 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered and the bar is lower. The description does add valuable behavior: results carry a found/fallback status and a confidence value where 0 means placeholder, which tells the agent results may be degraded. It stops short of explaining fallback triggering conditions or any rate/caching behavior.

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?

Two sentences with no filler: purpose first, then the exact per-query return fields. The parenthetical clarifying that confidence 0 means placeholder is the highest-value detail and is placed inline where it's needed.

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?

There is no output schema, so the description carries the burden of disclosing return shape, and it does so thoroughly (status, confidence, name, source URL, size, public image URLs). Only the cost of partial/failed batch lookups and output ordering remain unaddressed for a 20-item batch tool.

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 `queries` parameter is fully described in the schema itself, including the domain/product-name forms and the 20-item cap. The description adds nothing about query syntax or ordering beyond that, so the baseline of 3 applies.

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: "Look up logos for domains or product names." An agent knows exactly what it retrieves, but nothing distinguishes it from the sibling get_logo_image (single-image fetch) or logo_set, so the boundary between these tools must be inferred.

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 only implied by the batch-oriented input (array of up to 20 queries). There is no explicit statement of when to call this versus get_logo_image or logo_set, and no guidance on what to do when a lookup returns a fallback.

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