Skip to main content
Glama

Eveoy — Verified In-Store Foot Traffic ($24.99/customer)

by com.eveoy

Check Eveoy order status

check_order_status
Read-onlyIdempotent

Look up the status of an Eveoy order by its Stripe Checkout session id.

Use this when the user wants to:

  • Check whether an order was paid

  • See the order total and size for a checkout session

Trigger phrases include: "check my order", "order status", "did my payment go through", "status of session cs_...".

Returns: { customer_email (masked), locations, customers_per_location, total_cents, status, guarantee_type, top_sku_price_cents, shopper_bonus_cents, fee_breakdown { base_cents, sku_cents, bonus_cents } }.

Do NOT use this for: creating an order (use start_checkout) or pricing (use get_pricing). Requires the cs_... session id from a prior checkout.

Cost: free. Latency: fast. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesStripe Checkout session id (cs_...).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. Description adds 'Read-only', 'Cost: free', and 'Latency: fast', which supplement but do not vastly exceed the annotation coverage. No contradictions.

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 concise, uses bullet points, and front-loads the core purpose. Every sentence adds value without redundancy.

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?

The tool is simple, and the description covers purpose, usage guidelines, behavioral traits, and return fields. No output schema, but return values are sufficiently described. Complete for an agent.

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?

The input schema covers the single parameter (session_id) fully with description and constraints. The description reiterates the format (cs_...) but adds minimal semantic value beyond the schema.

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 specifies the tool's action ('look up the status of an Eveoy order by its Stripe Checkout session id') and distinguishes it from sibling tools like start_checkout and get_pricing.

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?

Explicitly states when to use (check order status, see payment, total, size) and when not to use (creating order or pricing), with trigger phrases and alternative tool names.

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

All Eveoy — Verified In-Store Foot Traffic ($24.99/customer) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: information lookup, booking, pricing, checkout, order status, etc. No two tools overlap in functionality; descriptions clearly delineate boundaries.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores (e.g., ask_eveoy, get_pricing, start_checkout, list_industries). No mixing of conventions.

Tool Count5/5

11 tools cover the full customer journey for a sales platform without being excessive. Each tool serves a specific, necessary function and fits within the typical 3-15 range.

Completeness4/5

Core workflows (information, pricing, checkout, order status, demos, human handoff) are covered. However, the ask_eveoy tool refers to a non-existent 'search_directory' tool, indicating a minor gap in the tool surface.

Resources