Skip to main content
Glama
Sign In

AisleNode Local Commerce (Meta Muse & Claude MCP)

by io.github.marvo-bd
OverviewDiscussionsAdmin

create_order

Reserve in-stock items at a local physical store and generate a zero-PII, non-custodial checkout URL. The shopper completes payment and delivery details directly on the verified merchant checkout page.

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": {
      "store_id": "<store_id>",
      "items": "<items>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesArray of products and quantities to reserve
store_idYesUUID of the verified physical store
agent_sourceNoIdentifier of the calling AI agent (e.g. "meta_muse", "claude_desktop")meta_muse

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 non-readOnly, non-idempotent, non-destructive and open-world. The description adds real value beyond them: it is zero-PII, non-custodial, and the shopper completes payment on the verified merchant page, so the agent knows this tool never handles payment data. It does not warn that repeat calls create duplicate reservations despite idempotentHint=false.

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 sentences, front-loaded with the core action, zero filler. Each sentence adds either the operation or the payment-handoff boundary.

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 exists, and the description tells the agent the return is a checkout URL, plus who completes payment. The main remaining gap is reservation lifetime/duplicate behavior for a non-idempotent mutation.

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%, including nested product_id/qty descriptions and a default for agent_source, so the schema carries the semantics. The description adds no format or constraint detail beyond it; baseline 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?

States a specific verb and resource: reserve in-stock items at a physical store and generate a checkout URL. The reservation/checkout framing clearly sets it apart from search_catalog and check_order_status, though no sibling is named 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?

Implies the usage context (after finding products via search_catalog, with store_id, to hand off to the shopper) but never states when to use it versus alternatives, nor any exclusions or prerequisites such as stock verification or reservation expiry.

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

All AisleNode Local Commerce (Meta Muse & Claude MCP) toolsInspect
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