Skip to main content
Glama

Highlight shared code

crabrix_select
Idempotent

Shares this MCP participant's selection in other editors using UTF-16 offsets and requires the expected project revision.

Instructions

Show this MCP participant's selection in other editors. Positions use UTF-16 offsets, not bytes. Requires the latest project revision; cannot split a Unicode surrogate pair.

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": {
      "path": "<path>",
      "anchor": "<anchor>",
      "head": "<head>",
      "expectedRevision": "<expectedRevision>"
    },
    "name": "crabrix_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
headYes
pathYes
anchorYes
expectedRevisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / expectedRevision / pattern
      Previous value: -"^[a-f0-9]{64}$"New value: +"^(?:[a-f0-9]{32}|[a-f0-9]{64})$"
  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 idempotent=true, destructive=false, and openWorldHint=true, so the safety profile is largely covered. The description adds genuinely non-obvious behavior: positions are UTF-16 offsets rather than bytes, the call is gated on the latest project revision, and a selection cannot split a surrogate pair — these are real failure/precondition semantics. It stops short of saying what happens when the revision is stale or what the broadcast does to other participants over time.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what the tool does, followed by the two constraints that most affect correct invocation. Every sentence carries information an agent needs; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four required parameters and no schema descriptions or output schema, the description supplies the most dangerous missing pieces (offset unit, revision precondition, surrogate-pair rule). It leaves gaps an agent would care about: what error a stale revision produces, whether the highlight persists or is transient, and what the call returns.

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 description coverage is 0%, so the description must carry the parameter burden, and it does partially: it explains the unit for the anchor/head integer offsets (UTF-16 code units, not bytes) and implies expectedRevision is compared against the current project revision. The 'path' parameter is never mentioned and no example values or range semantics are given, so the compensation is good but incomplete.

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?

The description gives a concrete verb and resource: 'Show this MCP participant's selection in other editors', which is far clearer than the opaque name 'crabrix_select'. It does not reference any sibling, but none of the listed siblings appear to be a competing selection/highlight tool, so differentiation is less critical.

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?

A prerequisite is stated ('Requires the latest project revision'), which tells the agent a precondition must be satisfied before calling. However, there is no explicit when-to-use guidance, no when-not-to-use, and no named alternative among siblings such as crabrix_handoff or crabrix_status.

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