Cosmic Good Boy shop

Delivery and shipping estimate

delivery_estimate

Read-onlyIdempotent

Earliest and latest delivery date if ordered today, and the shipping price options, for one or more products together (pieces from different print facilities travel as separate parcels).

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": {
      "slugs": "<slugs>"
    },
    "name": "delivery_estimate"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Shop language for names, copy and links	en
`slugs`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond that: the estimate is a snapshot based on ordering today, and multi-product orders can produce multiple parcels because pieces originate from different print facilities. It does not mention failure modes for unavailable or invalid product slugs.

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?

A single front-loaded sentence that states the returned values first and then the input scope. The parenthetical about separate parcels is short and carries real information, so no clause is wasted.

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?

With no output schema, the description correctly spends its words describing the return shape (date range plus shipping price options), which is the main thing the agent needs. The gap is minor: nothing is said about language effects on returned copy or behavior with invalid slugs.

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 50%: the lang parameter is documented in the schema, but slugs has no description. The description compensates partially by framing the input as 'one or more products together', implying slugs are product identifiers and that combinations are supported, without stating format or the 10-item cap.

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 names the concrete outputs (earliest and latest delivery date, shipping price options) and the input scope (one or more products combined), which is far more specific than the title's generic 'Delivery and shipping estimate'. It stops short of naming the sibling shipping_and_returns or stating how the two differ, so the agent must infer that this one is an estimate rather than policy lookup.

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?

The phrase 'if ordered today' implies the pre-purchase context in which this tool applies, and the parenthetical about separate parcels hints at when results are non-trivial. There is no explicit statement of when to prefer this over shipping_and_returns or when it is inappropriate, so guidance is only implied.

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

All Cosmic Good Boy shop tools Inspect

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

Need Help?