Skip to main content
Glama

ARC (arcreport.ai): can an agent reach checkout?

Merchant guide

guide
Read-onlyIdempotent

Call this when a person at a store (a CEO, a marketing or e-commerce manager, or a developer) asks where their store is on the journey to AI assistants, what to do next on their platform, or how stores in their category compare. Not for an agent about to check out: use before_checkout for that. Returns the store's place on ARC's journey map (arc-journey/v1: 5 stages, each met, not met or "Not measured" with its date; not measured is not a no, and there is no score or grade), the next 3 steps for its platform at the chosen depth with source links and an as-of date (a platform fact ARC has not sourced says "Not yet documented by ARC"), how many stores ARC checked in its category and on its platform and how many meet each stage (counts with denominators and the snapshot date), and up to 5 named stores that meet the furthest stage (ordered only by stage reached, then the newest reading). role: ceo, manager or developer sets depth (basics, detail or implement) unless depth is given. Send platform alone for the platform guide with no store. Example: guide({"store":"gymshark.com","role":"manager"}) → {"answer":"gymshark.com: Meets stages 1, 2, 3 and 4. Not met: stage 5. Saved check 16 Oct 2026.","stages":[…],"next_steps":[…],"comparison":{…},"examples":{…}}. Saved checks only: no store fetch, no scan, no login. Advisory; ARC stops before payment. Every answer carries checked_at (the saved check it rests on; for a list, the oldest) and stale (true when that check is 24 hours old or older, or has no time). Errors: {error:{code, message, next_step}}.

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

Input Schema

NameRequiredDescriptionDefault
roleNoWho is asking. Sets depth: ceo basics, manager detail, developer implement.
depthNoHow much detail. Default from role, else basics.
storeNoStore domain or URL, such as gymshark.com. Leave out and send platform for the platform guide alone.
categoryNoCategory for a platform-only call, such as footwear or apparel. A store uses its own category.
platformNoshopify, magento, salesforce, woocommerce, bigcommerce, wix, squarespace or other. Overrides the platform ARC detected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnly/idempotent annotations, it discloses operating constraints that matter: saved checks only, no store fetch, no scan, no login; advisory and stops before payment; every answer carries checked_at and stale (true at 24h+ or missing time); errors return {code, message, next_step}. It also pre-empts misreads of the data model — 'not measured is not a no, and there is no score or grade' — and documents the 'Not yet documented by ARC' placeholder. None of this contradicts the annotations.

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?

Front-loaded with the trigger and the sibling exclusion, and with no output schema the long return-value list earns its place; the concrete example call and response is high-value. The cost is that everything sits in one dense paragraph of nested parentheticals, which is harder to scan than a short structured list would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex, 5-optional-parameter, no-required-parameter tool with no output schema, and the description still covers call variants, defaults, return shape, freshness semantics, error shape, and hard boundaries (saved checks only, advisory). Nothing an agent needs to invoke it correctly or interpret the answer is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining cross-parameter behavior the schema cannot: role sets depth unless depth is given, platform alone triggers the platform guide with no store, and store calls ignore the category parameter. It does not, however, add format examples for the free-text store or category values beyond the schema's own examples.

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?

The description names a specific resource (a store's position on ARC's AI-assistant journey, next steps, peer comparison) and the audience (CEO, marketing/e-commerce manager, developer). It explicitly separates itself from the checkout-time sibling: 'Not for an agent about to check out: use before_checkout for that.' An agent can pick this tool without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a positive trigger (a person at a store asks where they are, what to do next, or how their category compares), an explicit exclusion with the named alternative (before_checkout), and a variant call shape ('Send platform alone for the platform guide with no store'). The role-to-depth precedence rule is also spelled out, so the agent knows defaults without guessing.

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