Skip to main content
Glama

Cursor bridge diagnostics

cursor_status
Read-onlyIdempotent

Checks Cursor setup without spending quota, covering agent-intern bridge updates, cursor-agent version, login status, and chat storage; run it first when a call reports 'not found'.

Instructions

Check the Cursor setup. Spends no quota; run it first when a call says "not found". Its bridge version row says when a newer agent-intern release is out: if so, tell the user. Also checks cursor-agent's version, whether you're logged in (cursor-agent status), and where cursor keeps its chats.

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": "cursor_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.21.0

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false). Beyond that, the description adds a genuinely useful cost trait — 'Spends no quota' — and enumerates the individual checks it performs, which is real added context. It stops short of describing failure modes or how a partially broken setup is reported, so a 3 is fair.

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?

The core action is front-loaded in the first sentence, followed by the cost/trigger guidance and then the checklist of checks. Every sentence carries either a trigger condition or a fact the agent needs; no padding.

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 zero parameters, a full annotation set, and an output schema available, the definition needs only purpose, trigger, and post-result behavior — all present. The one gap is what an agent should do if the diagnostic returns ambiguous or unexpected output, but the essentials are covered.

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 takes no parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly adds no parameter talk, which is appropriate.

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 concrete verb and resource ('Check the Cursor setup') and immediately frames what it reports on: bridge version, cursor-agent version, login state, and chat storage location. It is distinguishable from the cursor_ask/cursor_continue siblings because it only inspects, but it does not name any sibling directly, so it falls just short of a 5.

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 triggering condition — 'run it first when a call says "not found"' — plus a follow-up instruction to tell the user when the bridge version row indicates a newer release. What's missing is any explicit when-not guidance or a named alternative (e.g. cursor_ask) for the case where the setup is fine.

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