Skip to main content
Glama
Sign In

Annalist

by io.github.ryanroskowski
OverviewDiscussionsAdmin

Check a website before shopping there (free)

annalist_verify_store
Read-only

Free. Before an agent shops on a website, get its signed Annalist check from our weekly commerce census: is it a store, does it take agent checkout (UCP or ACP) and at which MCP endpoint, which payment handlers, how many countries it ships to, and which AI agents its robots.txt blocks. Verify the signature with the key at /.well-known/annalist-key.json.

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

Input Schema

NameRequiredDescriptionDefault
domainYesthe site, for example allbirds.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover read-only/open-world, so the bar is lower. The description adds meaningful behavior: it is free, the data comes from a weekly commerce census, the response is cryptographically signed, and it tells the agent where to find the verification key. It does not discuss rate limits or response size, but the data-freshness and signing context are valuable additions.

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 cost and timing, then the payload contents, then the verification key location. Every clause earns its place.

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?

No output schema, so the description usefully enumerates the returned fields and how to validate the signature. What remains missing is failure behavior (e.g. what happens for an uncatalogued domain) and any pagination/rate-limit notes.

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 100% and there is a single 'domain' parameter with an example already in the schema. The description does not add format or handling guidance for the parameter, 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+resource (verify store / get signed check) and enumerates exactly what data is returned: store status, agent checkout protocol and MCP endpoint, payment handlers, shipping countries, robots.txt agent blocks. Distinguishable from siblings like annalist_verify_mcp and annalist_verify_service by focusing on commerce stores.

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?

Explicitly frames the when: 'Before an agent shops on a website.' Also says the check is free. However, it does not name the alternative sibling tools (e.g. annalist_verify_mcp/annalist_verify_service) or state when NOT to use this, so it falls short of a 5.

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

All Annalist toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources