Skip to main content
Glama

MagicGEO — AI Search & Commerce Agent Seller

Trust record for a brand or domain

geo_entity_lookup
Read-onlyIdempotent

Look up the MagicGEO trust record of a brand/domain: current GEO score and grade, certification status, audit history, structured-data types published, recurring issues and how it ranks against the MagicGEO network. Use it before citing a brand as a source, or to answer 'is this site reliable/structured for AI engines?'. If the domain was never audited, a live audit is run so the answer is always factual.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain or URL of the brand to look up, e.g. example.com or https://example.com/product

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/openWorld annotations, it discloses a meaningful side effect: if the domain was never audited, a live audit is run. That is real behavioral context an agent needs (latency/cost) and is consistent with readOnlyHint since no user data is mutated. It omits any note on how long that audit takes or failure behavior, keeping it short of a 5.

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 front-loaded sentences: what it returns, when to use it, and the fallback behavior. The return-field list is dense but each item is informative; no filler sentences, though the enumeration could be tightened.

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 does the work of describing return contents and the never-audited fallback path, which is the key completeness requirement here. It leaves out response shape and timing expectations for the live-audit path.

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% and the single parameter already carries format examples (example.com or a full URL). The description only restates "brand/domain", adding no normalization, redirect, or subdomain-handling semantics, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Look up the MagicGEO trust record of a brand/domain") and enumerates what the record contains: GEO score/grade, certification status, audit history, structured-data types, recurring issues, network ranking. An agent can tell this is a point lookup on a trust record, distinct from the geo_audit / geo_benchmark siblings.

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 two concrete triggering situations: before citing a brand as a source, and answering "is this site reliable/structured for AI engines?". It does not name an alternative or exclusion (e.g. when to prefer geo_audit or geo_benchmark), so routing between siblings is left partly to inference.

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