Skip to main content
Glama

MagicGEO — AI Search & Commerce Agent Seller

State of GEO benchmarks

geo_industry_stats
Read-onlyIdempotent

Anonymized aggregate benchmarks from the MagicGEO network (average GEO score, schema/meta/alt coverage, per-category averages). Use it to cite industry reference figures on AI readiness of e-commerce catalogs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "geo_industry_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world scope, so the safety profile is covered. The description adds genuine context beyond that: the data is anonymized, aggregated across a network rather than tenant-specific, and contains named metric families. It omits freshness or update cadence, which would matter for a benchmarking tool.

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?

Two sentences, front-loaded with the resource and its contents, followed by the intended use. No filler or marketing padding. Slightly tighter phrasing of the contents list would improve it marginally, but nothing is wasted.

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 parameters and no output schema, the description carries the burden of describing what comes back, and it does so by naming the metric families returned. It does not state the aggregation window or whether figures are refreshed, a meaningful gap for a benchmark tool, but overall it is sufficient to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The description does not need to explain inputs, and it correctly spends its words on return content instead.

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 clearly states what the tool returns: anonymized aggregate benchmarks from the MagicGEO network, enumerating average GEO score, schema/meta/alt coverage, and per-category averages. That is specific enough for an agent to understand the resource. It stops short of differentiating from the sibling geo_benchmark, whose scope is left ambiguous.

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 second sentence gives a concrete use case: citing industry reference figures on AI readiness of e-commerce catalogs. That is real when-to-use guidance rather than nothing. However, it offers no exclusions or tie-breaker against geo_benchmark, so an agent facing both tools must still guess which applies.

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