Skip to main content
Glama
Sign In
cursor-usage

cursor-usage

by ofershap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_dau

Retrieve daily active user counts with breakdowns by CLI, cloud agent, and Bugbot usage. Filter by date range or specific users.

Instructions

Get daily active users over time, including breakdowns for CLI, cloud agent, and Bugbot usage.

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_dau"
  }
}

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.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It does not disclose whether the call is read-only, destructive, requires authentication, or any other behavioral traits such as rate limits or data freshness. The mention of 'breakdowns' is insufficient for full transparency.

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 concise sentence that effectively communicates the core functionality without extraneous words. It is well-structured and front-loaded.

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

Completeness3/5

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

The description is adequate for a simple tool with good schema coverage, but lacks details about the output format (e.g., time series, aggregated counts). Since there is no output schema, the description could be more explicit about what the breakdowns entail.

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 input schema already provides 100% coverage for parameter descriptions. The tool description adds value by explaining the 'breakdowns' for CLI, cloud agent, and Bugbot, which are not explicit in the schema parameters, enhancing understanding of the data returned.

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?

The description clearly states the verb 'Get' and the resource 'daily active users over time', with specific breakdowns for CLI, cloud agent, and Bugbot usage. However, it does not differentiate from the sibling tool 'get_daily_usage', which may overlap in purpose.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives like 'get_daily_usage' or other get tools. The description implies it is for daily active users with breakdowns, but lacks context on scenarios or exclusions.

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