MUDD World Sanctuary

expedition_send

Send one owned active RESLA Drone for 10 minutes to Garden or Library. Requires play + expeditions, UUID requestId. One departure/account/UTC day across clients. Free, no fuel or charges. Garden brings 1 random existing ingredient using Garden rarity odds; Library picks uniformly from public readable text works. Skip this account's last 7 finds per destination unless the pool is exhausted. Picks are saved at departure. That copy cannot be gifted/dismantled until collection. No equip required.

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": {
      "requestId": "<requestId>",
      "inventionId": "<inventionId>",
      "destination": "<destination>"
    },
    "name": "expedition_send"
  }
}

Input Schema

Name	Required	Description	Default
`requestId`	Yes
`destination`	Yes
`inventionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026
RemovedNov 6, 2026
AddedOct 29, 2026

TDQS

A4.1/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does well: it discloses duration, cross-client daily rate limit, loot-selection rules per destination, the 7-find skip rule, that picks are saved at departure, and that the copy is locked from gifting/dismantling until collection. These are exactly the non-obvious behaviors an agent needs.

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?

Front-loaded with the core action and constraints in the first clauses, then mechanics. Dense with abbreviations ('play + expeditions', 'RESLA') but nearly every sentence earns its place given the complexity.

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 mutation with no annotations and no output schema, the description covers preconditions, constraints and loot behavior thoroughly. The main gap is that it never indicates what the call returns (expedition record, confirmation), which an agent lacks since there is no output schema.

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?

At 0% schema coverage the description must compensate. It explains the destination enum semantics well (garden=random ingredient, library=uniform public text) and ties inventionId to 'owned active RESLA Drone', but it never explains requestId's role beyond the UUID already in the schema (presumably idempotency), leaving one parameter's purpose undocumented.

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+resource+destinations: 'Send one owned active RESLA Drone for 10 minutes to Garden or Library.' The action is unambiguous and distinct from siblings like expedition_collect/expedition_status, though it never explicitly names the alternatives it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear preconditions ('Requires play + expeditions', 'No equip required', 'Free, no fuel or charges') and a hard constraint ('One departure/account/UTC day across clients') that effectively tells the agent when the tool cannot be used. It stops short of naming the collect/status siblings as the next step.

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

All MUDD World Sanctuary 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?