Skip to main content
Glama
Sign In
cursor-usage

cursor-usage

by ofershap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_plans

Retrieves plan mode adoption data: which models are used in plan mode and how often, with optional date range and user filters.

Instructions

Get plan mode adoption: which models are being used in plan mode and how often.

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

Input Schema

NameRequiredDescriptionDefault
usersNoComma-separated emails to filter by specific users
endDateNoEnd date. Formats: "YYYY-MM-DD", "today", "yesterday". Default: "today"
startDateNoStart date. Formats: "YYYY-MM-DD", "7d", "30d", "today", "yesterday". Default: "30d"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the tool's purpose but does not mention any behavioral traits such as read-only nature, required permissions, rate limits, or side effects. The description is minimal in this regard.

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 of 13 words, directly stating the purpose without any fluff. It is front-loaded and efficient.

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

Completeness2/5

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

Given no output schema, the description should explain the return format. It only says 'which models are being used and how often' but does not specify the structure (e.g., list of objects, fields). With 3 parameters but no output details, the description is incomplete for a reporting tool.

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 description coverage is 100%, so baseline is 3. The description adds no additional meaning beyond what the schema provides for the parameters. It does not explain their use cases or format constraints beyond the schema's own descriptions.

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 verb 'Get', the resource 'plan mode adoption', and specifies what information is returned: which models are used in plan mode and how often. This distinguishes it from siblings like get_model_usage, which likely covers all model usage, and get_daily_usage, which is broader.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool vs alternatives. There are no prerequisites, limitations, or explicit context for when to prefer this over sibling tools like get_model_usage or get_daily_usage.

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