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

cursor-usage-mcp

by udah1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Skip the current available update

dismiss_update

Record the current remote version as skipped when a user declines an update, preventing repeated alerts until a newer version is released.

Instructions

Call this when the user declines an available update. Records the current remote version as skipped so get_usage won't surface it again — until an even newer version appears on GitHub.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it records the skip state, affects get_usage, and is temporary until a newer version appears. This clarifies side effects and temporal scope without contradicting any structured data.

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 a single sentence that front-loads the call condition and immediately explains the effect. Every phrase earns its place with no 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 tool with no parameters and no output schema, the description is complete: it tells when to use, what it does, and the impact on get_usage. The caveat about newer versions covers edge behavior.

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, which sets a baseline of 4. The description adds no parameter-specific details (as none exist), but it conveys the tool's action and effect, which is sufficient for a no-parameter tool.

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: recording the current remote version as skipped so get_usage won't surface it. It uses specific verbs ('Call this when the user declines') and names the affected sibling tool (get_usage), distinguishing it from other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly instructs when to call ('when the user declines an available update') and implies when not to call (when the user accepts). It also references get_usage as the alternative that would otherwise surface updates, providing clear contextual guidance.

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