SendaMeal Storefront

search_products

Search products by a term

Arguments: term - the search term to look for products. It should be at least 3 characters long. cursor - optional, used for pagination. If provided, it will return the next page of results after.

Pagination: Supports pagination with 'cursor' arguments. If 'cursor' is not provided, it will return the first page of results. Value for 'cursor' can be obtained from the 'nextCursor' field in the response. If 'nextCursor' is null, it means there are no more results to fetch. If value of cursor is null (or a string representation of 'null') dont send it in the payload.

Results: Each product includes 'requiresFileUpload'. When true, the product has a required file-upload option (e.g. "upload your design") and shouldn't be added to cart through this assistant. Do not attempt to purchase it — tell the user it must be ordered on the website.

Flow:

Call this tool with a 'term' argument and optionally with 'cursor' to search for products.
- if you find a matching product, call 'get_product_details' with the product ID to get its variants and options (if any).
- if 'requiresFileUpload' is true, inform the user the product needs a file upload and cannot be purchased here.
Call 'add_item_to_cart' with results of 'search_products' and 'get_product_details' (variant) tools to add the product to the cart.
- [IMPORTANT] If product has variants ask user to pick

Input Schema

TableJSON Schema

Name	Required	Description
`term`	Yes
`cursor`	No
`context`	No	Additional information about the request such as user demographics, mood, location, or other relevant details that could help in tailoring the response appropriately. Should not contains PII.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`message`	No
`success`	Yes
`products`	Yes
`nextCursor`	No

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries full responsibility. It thoroughly explains pagination via cursor, the meaning of nextCursor, and when to omit the cursor. It also reveals the requiresFileUpload behavior, preventing incorrect purchases. This is extensive behavioral disclosure.

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?

The description is well-structured into Arguments, Pagination, Results, and Flow sections. It's longer than typical but every section earns its place by providing essential operational guidance. Slight verbosity in the flow section, but it's useful context.

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 description is complete for the tool's complexity. It covers pagination, result content, and the order of operations with sibling tools. The output schema is available, so return values don't need to be enumerated, but the nextCursor field is highlighted. Enough for an agent to use the tool correctly without additional information.

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?

The description adds meaning for term (minimum 3 characters) and cursor (pagination semantics), which are not described in the schema. However, the 'context' parameter is not mentioned in the description, but it already has a schema description. Given the low schema coverage, the description compensates well for the primary parameters but leaves context unaddressed.

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 clearly states 'Search products by a term' with a specific verb and resource. It distinguishes itself from siblings by describing the search-first flow, making it evident this is the entry point for product discovery.

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?

Provides an explicit flow: call search_products first, then get_product_details for matches, and add_item_to_cart afterward. It also gives a clear when-not-to-use via the requiresFileUpload warning, telling the agent not to add such products to cart.

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

All SendaMeal Storefront tools Inspect

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.1/5.0

Disambiguation5/5

Each tool has a clear, distinct purpose: searching products, fetching details, adding/removing/updating cart items, and creating a checkout URL. There is no functional overlap between the six tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., search_products, add_item_to_cart, create_checkout_url). This makes the toolset predictable and easy to navigate.

Tool Count5/5

Six tools is well-scoped for a storefront server, covering the essential product discovery and cart management lifecycle without being bloated or too sparse.

Completeness3/5

The toolset covers product search, product details, cart additions/updates/removals, and checkout URL generation, but lacks a way to view the current cart contents. This is a notable gap since agents need to know what is already in the cart to manage it effectively.

Resources

Need Help?