Skip to main content
Glama

Matched logo set

logo_set
Read-only

Return logos as a matched set for one background and size: same visual weight and padding, full color or one tone, with warnings when a logo will not read on the background. Missing logos become neutral stand-in tiles marked standIn: true. Includes a row_url that renders the whole set as one PNG strip.

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

Input Schema

NameRequiredDescriptionDefault
bgNoSlide background: hex like ffffff or 1f2937.
padNo
sizeNo
toneNocolor
colorNoHex color for tone=mono.
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.9/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld; the description adds substantial behavior beyond that — normalization of visual weight and padding, a color/mono mode, warnings when a logo will not read on a given background, neutral stand-in tiles flagged with standIn: true, and a row_url that renders the set as one PNG strip. These are exactly the outputs an agent needs to anticipate and act on.

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?

Three compact sentences, no filler, with the defining concept (matched set for one background and size) front-loaded. The density of clauses in the first sentence is slightly high but each clause carries real information.

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 must carry the return contract, and it largely does: it names the per-logo standIn flag and the aggregate row_url strip. It stops short of saying what the primary payload looks like (a list of image URLs or tiles), leaving one gap for a six-parameter 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 description coverage is 50%. The description explains the intent behind bg, size and tone (one background, one size, full color or one tone) and connects background choice to warning behavior, which the schema does not. However, it says nothing about pad, about color being required when tone=mono, or about the practical limits of the queries array (up to 20 names).

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?

The description states a specific verb and resource: 'Return logos as a matched set for one background and size', and clarifies the consistency axis (visual weight, padding, color vs mono). That distinguishes it from get_logo_image and find_logos in spirit, though it never names those siblings explicitly.

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 implied rather than stated: 'matched set for one background and size' suggests calling this when several logos must look consistent on a single slide. There is no explicit when-not guidance, no mention of when to prefer get_logo_image for a single asset, and no prerequisites (e.g. resolving names via find_logos first).

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