Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

BIMI record check

bimi
Read-onlyIdempotent

Use when the user asks why a brand logo does not show in inboxes, or about BIMI. Returns the BIMI record, logo and certificate URLs and whether DMARC is enforced as BIMI requires. The logo is not downloaded. Ex: 'Is BIMI set up for example.com?'. Free trial without an API key: a few calls a day.

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": {
      "domain": "<domain>"
    },
    "name": "bimi"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA public domain name, e.g. example.com.
selectorNoOptional BIMI selector (default: default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), and the description still adds useful detail beyond them: the logo binary is not downloaded, and without an API key usage is limited to a few calls a day. The rate-limit disclosure is exactly the kind of operational constraint annotations cannot express; no output shape is described, but no output schema exists either.

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?

The usage trigger is front-loaded, followed by returns, a behavioral caveat, and an example — a logical order with no filler sentences. The trailing free-trial note is slightly promotional in tone but does carry rate-limit 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 only two parameters, complete schema coverage, and rich annotations, the description covers what an agent needs: when to call, what comes back, and the fact that no logo file is fetched. The only minor gap is that the selector parameter's effect on results is never explained.

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 100%, so the domain format and the optional selector (default 'default') are already documented in the schema. The description adds no meaning about the selector or how it affects the lookup, 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 resource (the BIMI record) and enumerates the concrete returns: BIMI record, logo URL, certificate URL, and DMARC enforcement status. It is clear what the tool does, but it does not explicitly position itself against close siblings such as dmarc or dkim, so the agent must infer the split.

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?

Gives an explicit trigger scenario ('why a brand logo does not show in inboxes, or about BIMI') plus a sample query, which is enough for an agent to recognize the request type. It lacks any when-not-use guidance or a named alternative for adjacent questions like plain DMARC lookups.

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.