Skip to main content
Glama
andreilungeanu

Cursor Delegate

by andreilungeanu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

doctor

Read-onlyIdempotent

Run diagnostics when delegation fails or agent.found is false. Checks plugin version, MCP client capabilities, and cursor-agent launcher resolution, with an optional deep handshake to verify usability.

Instructions

Setup diagnostics: plugin version, MCP client capabilities, cursor-agent launcher resolution. Run when delegation fails or agent.found is false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deepNoRun an ACP handshake (start → initialize → newSession) to verify the agent is usable; adds models, modes and the current model's options.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / deep / description
      Previous value: -"When true, run a lightweight ACP handshake (start → initialize → newSession) to verify the agent is usable"New value: +"Run an ACP handshake (start → initialize → newSession) to verify the agent is usable; adds models, modes and the current model's options."
  3. First observedv1.18.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered by structured data. The description adds the failure-triage framing but says nothing about cost, side effects of the deep handshake, or output shape beyond the schema-documented parameter.

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?

Two sentences, no filler: the first says what is checked, the second says when to run it. The scoping and trigger are front-loaded and nothing is redundant.

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 read-only, single-optional-parameter diagnostic with no output schema, the description covers what is inspected and the invocation trigger. It is slightly thin on what the agent should do with the result, but nothing needed to call it correctly is missing.

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 coverage is 100% and the sole optional 'deep' parameter is thoroughly documented in the schema itself (ACP handshake, added models/modes/options). The description contributes no additional parameter meaning, so the baseline 3 applies.

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?

Names a concrete diagnostic resource and enumerates exactly what it inspects: plugin version, MCP client capabilities, cursor-agent launcher resolution. It is clearly not a delegation tool, so siblings delegate/cancel are implicitly distinguished, though 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete trigger condition: 'Run when delegation fails or agent.found is false.' That tells the agent when to reach for this tool rather than delegate. No explicit when-not or alternative routing, but the trigger is unambiguous.

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

Deploy Server

Other Tools