Skip to main content
Glama
Sign In
cursor-usage-mcp

cursor-usage-mcp

by udah1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Enable/disable the end-of-task follow-up question

set_followup

Enable or disable a follow-up prompt after each task, so the agent asks 'anything else?' via the UI, letting you respond and continue the conversation without manual interruption.

Instructions

Persists follow-up mode (default off): when on, get_usage tells the agent to end each task with a brief 'anything else?' question via the questions/options UI, so you almost always get a prompt you can respond to. Overridden by the CURSOR_USAGE_FOLLOWUP env var if set.

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": {
      "followup": "<followup>"
    },
    "name": "set_followup"
  }
}

Input Schema

NameRequiredDescriptionDefault
followupYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description itself discloses key behaviors: persistence (state change), default off, effect on get_usage, and the env var override. It does not mention permissions or return value, but for a boolean setter these are less critical. The description adds meaningful behavioral context beyond the tool name and title.

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 description is concise and well-structured, with the key information front-loaded. Every sentence adds value: the first explains the mechanism and effect, the second the override. No fluff or redundancy.

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

Completeness5/5

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

For a simple one-boolean setter with no output schema, the description is exceptionally complete. It covers purpose, default, effect on a related tool, and the env var override, which are the essential aspects. There is no missing critical information.

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 coverage is 0%, so the description must compensate. It does by explaining the meaning of the followup parameter indirectly: 'default off' and 'when on' indicate the boolean effect. However, it does not explicitly state that the followup parameter should be set to true to enable and false to disable, leaving a small gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: it persists a follow-up mode that affects get_usage's behavior. It specifies the action ('Persists follow-up mode'), the resource (end-of-task follow-up question), and distinguishes from siblings by tying it to get_usage. The default (off) and overriding env var add precision.

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?

The description implies when to use the tool: to control whether get_usage includes a follow-up question. It notes that when on, the agent will almost always get a prompt, and that an env var can override. It does not explicitly state 'use this instead of setting the env var' or list alternatives, but the context is clear enough for a simple setter.

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