Skip to main content
Glama

Get logo image

get_logo_image
Read-only

Return one logo as an image you can look at, plus its URL. Use to check a logo before placing it. Options: size (16-256), bg (hex, white, black), pad (0-40 percent), trim.

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": {
      "query": "<query>"
    },
    "name": "get_logo_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoBackground: hex like 1f2937, white or black. Default transparent.
padNo
sizeNo
trimNoCut empty border so the mark fills the frame.
queryYesA domain or product name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 the safety profile is covered and the description does not contradict it. The description adds that the response contains an actual viewable image plus a URL, which is useful behavioral detail the annotations cannot convey. It says nothing about external lookup failure modes for unknown names, or whether repeated calls are rate-limited, which matters given openWorldHint=true.

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?

Three short sentences: what it returns, when to use it, then the options list. The most decision-relevant information (image + URL) is front-loaded and there is no filler or repetition of schema fields.

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 takes on the burden of describing the return (an image plus its URL), and it enumerates the optional rendering controls. The remaining gap is what happens when the query does not resolve to a logo, which an agent would want to know before committing to this preview step.

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

Parameters4/5

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

Schema coverage is 60%, and the description compensates by naming all four optional knobs and adding meaning beyond the schema: pad is expressed as a percentage (0-40), size as a 16-256 range, and bg as hex/white/black. Only trim is listed without explanation, and the required query parameter is left entirely to the schema's own description.

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?

"Return one logo as an image you can look at, plus its URL" gives a specific verb (return/fetch), a specific resource (a single logo), and names the return shape. The singular "one logo" implicitly separates it from the plural search sibling (find_logos), but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

"Use to check a logo before placing it" supplies one concrete usage context, which is genuinely helpful for routing. However, it gives no when-not guidance, no mention of how it differs from find_logos or logo_set, and no prerequisites (e.g., whether the query must resolve to a known domain).

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