Skip to main content
Glama
Sign In

AisleNode Local Commerce (Meta Muse & Claude MCP)

by io.github.marvo-bd
OverviewDiscussionsAdmin

check_order_status

Read-onlyIdempotent

Check live fulfillment, payment, and courier dispatch status for an existing local retail order.

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": {
      "order_id": "<order_id>"
    },
    "name": "check_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesUUID of the order to inspect

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 the tool is read-only, idempotent, non-destructive, and open-world. The description adds useful domain context by specifying that it checks live fulfillment, payment, and courier dispatch status, though it does not describe error behavior or return shape.

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?

The description is a single front-loaded sentence with no redundant or filler text. Every phrase contributes to scope or purpose.

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?

For a simple one-parameter read-only status check, the description plus annotations and schema provide enough context to invoke it correctly. It could be more complete by mentioning expected return information or invalid-order behavior, especially since no output schema exists.

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?

There is only one required parameter and schema coverage is 100%, with order_id explicitly documented as a UUID. The description reinforces that the order must already exist but does not add syntax or format details beyond the schema.

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 states a specific verb and resource ('Check ... status') and names the status dimensions (fulfillment, payment, courier dispatch) plus scope ('existing local retail order'). It is clearly distinguishable from create_order, but does not explicitly mention its other siblings or exclusions.

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 'for an existing local retail order,' which signals this is the read path after an order exists. However, there is no explicit when-to-use/when-not guidance and no named alternative tool.

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