Skip to main content
Glama

Create a shared Rust Playground

crabrix_create

Creates a temporary encrypted source room and returns a private editable link for phone, tablet, or browser access; defaults to one hour, with no account or execution.

Instructions

Create a temporary encrypted source room when the user asks. Return its private editable link for opening in Crabrix on a phone/tablet or in the browser. Default lifetime: one hour. No account and no execution. Leave format unset: format 2 (stable file IDs) is for testing until Crabrix creates new rooms in it, and older apps cannot open it.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
filesNo
formatNo
editionNo
entryFileNo
lifetimeMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / format
      Added value: +{
      +  "anyOf": [
      +    {
      +      "const": 1,
      +      "type": "number"
      +    },
      +    {
      +      "const": 2,
      +      "type": "number"
      +    }
      +  ]
      +}
  2. Changed1 schema field changedv0.3.5
    • addedInput schema / properties / edition
      Added value: +{
      +  "enum": [
      +    "2021",
      +    "2024"
      +  ],
      +  "type": "string"
      +}
  3. First observedv0.3.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the write/network profile is known. The description adds substantive context beyond them: the room is encrypted and temporary, defaults to a one-hour lifetime, requires no account, and performs no code execution. It stops short of saying who can access the returned link or whether the room can be re-created with the same ID.

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?

Four sentences, front-loaded with the action and the return value before the caveats. The final format sentence is dense and slightly awkward ('is for testing until Crabrix creates new rooms in it'), but every clause carries operational information.

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 explains the return value (the private editable link) and its opening channels. For a six-parameter creation tool it covers lifetime, auth, and the format trap, but omits how name, files, edition, and entryFile behave, which is the main remaining hole.

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 description coverage is 0% across six parameters, so the description must compensate, and it does so for the single most error-prone one: format 2 is flagged as testing-only, unstable for older clients, and should be left unset. lifetimeMinutes is implicitly confirmed via 'Default lifetime: one hour'. The remaining parameters (name, files, edition, entryFile) get no meaning at all, including the nested files map, which leaves real gaps.

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?

A specific verb-plus-resource: 'Create a temporary encrypted source room'. It also states what the tool produces (a private editable link openable in Crabrix or the browser), which no sibling tool claims, so an agent can separate it from crabrix_connect, crabrix_select, and the runtime_* family without reading schemas.

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 trigger is given as 'when the user asks', which is implied usage rather than a concrete condition. It does supply real guidance for one parameter ('Leave format unset'), but gives no when-not conditions and never names an alternative sibling (e.g. connect to an existing room instead of creating one).

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