Logolark: company domain to logo, square icon and brand colour. Free, no key.
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlap. The purpose is singular and clearly defined, so an agent cannot misselect between alternatives.
The tool name 'find_logo' follows a clear verb_noun convention, which is consistent and intuitive. As there is only one tool, the pattern is trivially consistent.
The server has only one tool, which is below the typical 3-15 range, but given its highly focused purpose (logo and favicon lookup), this is a reasonable scope. The tool handles multiple inputs per call, reducing the need for additional helpers.
For its stated purpose, the tool is comprehensive: it retrieves logo and icon URLs, format, dimensions, transparency, brand name, and color. It accepts domains, URLs, or emails and processes up to five per call, covering the entire expected workflow without gaps.
Find a company's real logo and square icon from its own website, verified by downloading: logo URL, icon URL, format (SVG/PNG/ICO/WebP), pixel size, transparency, brand name and brand colour (hex). Use when you need a company's logo image or brand colour. Accepts domains, URLs or work emails; up to 5 per call.
| Name | Required | Description | Default |
|---|---|---|---|
| domains | Yes | Company domains, website URLs or work emails, e.g. "stripe.com", "https://www.notion.so", "jane@figma.com". Up to 5. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool read-only and idempotent, and the description adds that results are 'verified by downloading' from the company's own website, which explains the reliability mechanism. It does not mention rate limits or auth requirements, but for a read-only lookup this is a minor gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no wasted words. It front-loads the core capability and outputs, then gives usage guidance, making it easy to scan and act on.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, but the description enumerates the returned fields: logo URL, icon URL, format, pixel size, transparency, brand name, and brand colour. Together with the input constraints and annotations, this is sufficient for an agent to invoke and interpret the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the schema already documents accepted formats with examples and the 5-item maximum. The description repeats the accepted input types and limit but adds no significant new semantic meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action and resource: finding a company's 'real logo and square icon from its own website.' It also enumerates the returned fields, making the tool's purpose unambiguous even without sibling tools to differentiate from.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says 'Use when you need a company's logo image or brand colour,' giving a clear selection criterion. It also states accepted input types (domains, URLs, work emails) and the limit of 5 per call, so an agent knows exactly when and how to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
find_logoLogolark: company domain to logo, square icon and brand colour. Free, no key.
Company & brand data by domain or ticker/ISIN: industry, headcount, HQ, social, colors, logos.
Free — no API key required. Enrich by domain or name. Country, contacts, social profiles.
3DLogo.io, a browser 3D logo maker: 3D logos, 3D coins, 3D models from photos or prompts, embeds.
Add one secure layer between your agents and this server.
