Skip to main content
Glama

Connect to Crabrix

crabrix_connect

Join a user-authorized temporary Playground as a named MCP participant by passing an agent or person link, then read or edit according to the link's granted access.

Instructions

Join a user-authorized temporary Playground as a named MCP participant. Accepts an agent link (https://crabrix.com/mcp/…, including the form with #key=… after it) or a person link (…/playground/room/…#…); pass the whole link. This bridge joins the room directly. The full link grants this MCP host/model access to decrypted source. An edit link allows changes; a view link allows reading only. The phone and browser see this participant.

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

Input Schema

NameRequiredDescriptionDefault
linkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.2/5.0
Behavior4/5

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

Adds meaningful behavior beyond the annotations: the full link grants access to decrypted source, an edit link permits changes while a view link is read-only, this bridge joins directly, and the participant is visible to the phone and browser. That security and visibility context is exactly what annotations (readOnlyHint=false, openWorldHint=true) cannot convey. It omits session lifetime, failure behavior for malformed links, and whether joining persists until crabrix_disconnect.

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?

Information-dense and front-loaded, with the core action stated first and qualifying details after. A few fragments ('This bridge joins the room directly', 'The phone and browser see this participant') are clipped but each still carries a distinct fact, so there is little wasted text.

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 one-parameter join tool with no output schema, the description covers the accepted input forms, the access implications of the link, and the observable side effect of participation. Missing only recovery/error context for invalid or expired links and what a successful join yields, which keeps it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero schema description coverage on the single 'link' parameter, the description carries the whole burden and does so: it explains that the parameter is a URL, gives both accepted forms (https://crabrix.com/mcp/… with #key=…, and …/playground/room/…#…), and explains that the fragment encodes the access level. That is real semantic value the schema does not provide.

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 and resource: 'Join a user-authorized temporary Playground as a named MCP participant.' An agent can immediately tell this is the entry/joining step rather than an operation tool like crabrix_apply_changes or crabrix_select. It does not explicitly name which sibling to use for other cases, but the intent is unambiguous.

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 precondition guidance: you need a link, and it tells you which two link shapes are acceptable (agent link or person link) and to pass the whole link including the fragment. It does not state explicit exclusions or route to siblings such as crabrix_create, so it stops just short of full when/when-not guidance.

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