Smart Glasses Atlas

compare_smart_glasses

Read-onlyIdempotent

Compare two or three product IDs using source-linked specifications, indicative prices, strengths, caveats and country-specific feature status. Missing facts remain unknown; prices are not live quotes.

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": {
      "country": "<country>",
      "model_ids": "<model_ids>"
    },
    "name": "compare_smart_glasses"
  }
}

Input Schema

Name	Required	Description	Default
`country`	Yes	Explicit shopping country; GB means United Kingdom. Independent of interface language.
`language`	No	Content language, not the shopping country.	en
`model_ids`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds genuinely useful data-quality context beyond them: results are source-linked, prices are indicative rather than live quotes, and missing facts stay unknown instead of being inferred — important expectations for an agent summarizing output.

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 tight sentences, front-loaded with the action and scope, followed by a single caveat sentence that carries real information about prices and missing data. No filler or restatement of the tool name.

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 must convey what comes back, and it lists the comparison dimensions (specs, prices, strengths, caveats, feature status) plus trust caveats. It falls short of describing result structure or how the two or three products are ordered/presented, but an agent has enough to call it and interpret the response.

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 67%: country and language are well documented in the schema, but model_ids has no schema description and is only constrained structurally. The description compensates partially by calling them 'product IDs' and stating the count of two or three, and by tying country to 'country-specific feature status', but adds no format or ID-provenance guidance beyond that.

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 ('Compare') and resource ('two or three product IDs') and enumerates what the comparison surfaces: specifications, indicative prices, strengths, caveats, and country-specific feature status. It is clearly distinct from find_smart_glasses (discovery) and get_buying_links (purchase links), though it never names those siblings explicitly.

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?

Usage is implied by the 'two or three product IDs' framing, which tells an agent this is a post-discovery step once IDs are known. However, there is no explicit when-to-use/when-not guidance and no mention of the sibling tools or what to do if fewer than two IDs are available.

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

All Smart Glasses Atlas 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?