TPC Hosting Free Tools

BIMI check

bimi_check

Read-onlyIdempotent

Checks a domain's BIMI record and logo (SVG) for brand indicators in email clients.

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_check"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	A domain name such as example.com. A full URL or an email address is reduced to its domain.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds that both the DNS record and the fetched SVG logo are examined, which hints at an outbound HTTP fetch, but it says nothing about what happens when the record is absent, when the SVG fails validation, or how failures are reported.

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?

One sentence, front-loaded with the verb and resource, with zero filler. It is on the terse side given the tool's complexity, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of saying what the agent gets back; it names the record and the SVG logo but not whether the SVG is validated against the Tiny PS profile, nor what the pass/fail signal looks like. For a single-parameter read-only check this is adequate but leaves an agent guessing at result shape.

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 domain parameter is fully documented, including URL/email normalization, so the description does not need to restate it. Nothing in the description adds meaning beyond the schema, which is appropriate but minimal — baseline 3.

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 gives a specific verb and resource: it checks a domain's BIMI record and the SVG logo referenced by it, scoped to brand indicators in email clients. That makes it clearly distinct from the DKIM/SPF/DMARC authentication siblings, though it never names them or states what separates a BIMI check from a general DNS lookup.

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?

The mention of 'brand indicators in email clients' implies the check is about email branding rather than deliverability or authentication, but there is no explicit when-to-use, no prerequisite context (BIMI requires DMARC enforcement and typically a VMC), and no guidance on what to run instead if the user actually wants DMARC or SPF results.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TPC Hosting Free Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?