Skip to main content
Glama

MagicGEO — AI Search & Commerce Agent Seller

Benchmark URLs against each other

geo_benchmark
Read-onlyIdempotent

Audit several public URLs (a site and its competitors) and rank them by GEO score, so an AI can tell which source is the most structured, coherent and citable.

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": {
      "urls": "<urls>"
    },
    "name": "geo_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesBetween 2 and 5 public URLs to compare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety and repeatability profile is covered. The description adds that URLs must be public and that the operation produces a ranking by a composite quality score, but it does not disclose anything about runtime cost, failure handling for unreachable URLs, or how ties are treated.

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?

One sentence, front-loaded with the action and resource, with the purpose clause ('so an AI can tell...') giving the payoff without padding. Nothing is wasted and nothing essential is buried.

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 one fully documented parameter, read-only annotations, and no output schema, the definition needs to convey only the comparison intent and the return concept, both of which it does. The minor gap is that 'GEO score' and the ranking output format are not elaborated, though the surrounding terms (structured, coherent, citable) give enough orientation.

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 'urls' parameter already documents the 2-to-5 range and the 'public' constraint. The description adds only a light semantic framing (a site plus its competitors), which is marginal added meaning over the schema, 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?

The description names a specific verb ('Audit ... and rank') and a specific resource (several public URLs) and states the ranking criterion (GEO score). It is clear what the tool does, but it never explicitly contrasts itself with the sibling geo_audit, so an agent must infer that this is the multi-URL comparison variant.

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 parenthetical '(a site and its competitors)' implies the intended scenario: comparative benchmarking rather than auditing one page. However, there is no explicit when-not guidance and no named alternative for single-URL audits, so the agent has to infer the boundary from context alone.

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