Skip to main content
Glama

MagicGEO — AI Search & Commerce Agent Seller

Formatted, verifiable citation

geo_citation
Read-onlyIdempotent

Produce a ready-to-use citation block for a source URL, backed by a live MagicGEO GEO audit (score, grade, structured-data types, verification timestamp and verification endpoint). Use it when citing a brand, product page, catalog or author page and you need a trust signal.

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": {
      "url": "<url>",
      "style": "<style>"
    },
    "name": "geo_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic URL of the source to cite.
styleYesCitation output style. Defaults to json when null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld behavior, so the bar is lower, and the description still adds real substance: the citation is generated from a live external audit and carries score, grade, structured-data types, a verification timestamp and a verification endpoint. It does not cover what happens if the URL is unreachable or the audit fails, nor any latency/rate considerations for a live lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler. The primary action and its backing data are front-loaded, and the usage condition follows. Nothing repeats the title or the schema.

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?

There is no output schema, and the description compensates by enumerating what the citation block contains plus the verification artifacts an agent would otherwise have to discover. What's missing is how the output differs per style (json/markdown/plain) and failure behavior for unverifiable URLs, which matters for a live-lookup 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 100% for both parameters, so the schema already explains 'url' and the 'style' enum with its null default. The description reinforces that the input is a public source URL but adds nothing about style selection or URL constraints beyond the schema, so the baseline 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?

The description uses a specific verb and resource ('Produce a ready-to-use citation block for a source URL') and immediately explains that the block is backed by a live GEO audit. That contrasts implicitly with geo_audit, which returns raw audit data rather than a formatted citation, though no sibling is named explicitly.

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?

'Use it when citing a brand, product page, catalog or author page and you need a trust signal' gives a clear triggering context and even characterizes the user's intent. It stops short of naming an alternative (e.g. call geo_audit directly if you only want the score) or stating when not to use it.

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