Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Shuffle a list

random_shuffle
Read-only

Shuffle a comma- or line-separated list into a random order (Fisher-Yates with a cryptographic random source). Use for draw orders, seating and playlists. Example: items=1,2,3,4,5. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "items": "<items>"
    },
    "name": "random_shuffle"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesComma-separated items

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, non-idempotent and closed-world, and the description reinforces that with "reads or computes only and changes nothing." It adds genuinely new behavioral context the annotations cannot convey: the randomness source quality, and the critical operational note that each call is billed while failed calls are free, meaning a repeat shuffle costs money — which is exactly the practical consequence of idempotentHint=false. The one gap is that with no output schema, the shape of the returned shuffled list is never described.

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?

Everything is front-loaded: purpose and algorithm first, then use cases, then an example, then cost/idempotency caveats. Each sentence carries distinct information — the billing clause is not padding, since it changes retry behavior. It is dense and slightly packed with pricing detail, but no sentence is redundant with the schema or annotations.

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 single-parameter, annotation-rich utility, the description covers what matters to call it correctly: accepted input formats, the shuffle algorithm's quality, the fact that nothing is mutated, and the cost model including free failed calls. The only omission is how the shuffled result is returned, which has no output schema to cover it.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns above that by extending the schema's own wording: the schema says only "Comma-separated items" while the description explicitly permits line-separated input as well, a real behavioral difference an agent would otherwise miss. The worked example (items=1,2,3,4,5) also demonstrates the expected string format concretely.

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?

"Shuffle a comma- or line-separated list into a random order" states a specific verb and resource, and the parenthetical "(Fisher-Yates with a cryptographic random source)" pins down the mechanism so an agent knows this is a genuine uniform shuffle rather than a rotation or pick. Concrete use cases (draw orders, seating, playlists) further disambiguate it from siblings like random_pick or random_teams, which serve different output shapes.

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?

The description names three concrete situations (draw orders, seating, playlists) and an inline example input, giving clear positive guidance for when to reach for this tool. It stops short of explicit exclusions — it never says to use random_pick for a single winner or random_teams for grouped output — so the agent must infer the boundary from sibling names alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.