Skip to main content
Glama

Shared project and participants

crabrix_status
Read-onlyIdempotent

Reads current room status, including file paths, revisions, expiry, participants, and remote text selections, plus file IDs, conflicts, recovery rows, and blocked reasons when available.

Instructions

Read current file paths, revision, expiry, participant names and remote text selections. In a format 2 room also file IDs, conflicts, recovery rows and blocked reasons. No source text or private link is included.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crabrix_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
connectedYes
executionYes
connectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.5
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "connected": {
      +      "type": "boolean"
      +    },
      +    "connection": {
      +      "type": "string"
      +    },
      +    "execution": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "connected",
      +    "connection",
      +    "execution"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.3.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds valuable behavior beyond annotations: it lists returned fields, notes additional fields for format 2 rooms, and explicitly excludes source text and private links. No error or auth details are provided.

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?

Three short sentences, front-loaded with 'Read' and the data list. The privacy exclusion is a clean final constraint. 'Format 2 room' is slightly jargon-y but compact, and no words are 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?

For a zero-parameter read-only status tool with an output schema, the description is sufficient: it explains what status data is returned, room-format variations, and privacy boundaries. It could mention when to prefer sibling inspection tools, but the core is complete.

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?

The tool has zero parameters and schema coverage is 100%, so the description does not need to explain parameter meanings. The 0-parameter baseline of 4 applies, and no additional parameter semantics are required.

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 the verb 'Read' and enumerates the status resource: file paths, revision, expiry, participant names, remote text selections, plus extra fields for format 2 rooms. This clearly identifies a read-only status inspection distinct from mutation siblings like crabrix_apply_changes, although no sibling is named explicitly.

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?

No explicit when-to-use or when-not-to-use guidance is given. The read-only status nature implies it is for inspecting current room state, but alternatives such as crabrix_read_file or crabrix_runtime_inspect are not mentioned. Usage is only implied.

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