Skip to main content
Glama
Sign In
cursor-usage

cursor-usage

by ofershap
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_mcp_usage

Retrieve usage statistics for MCP servers and tools, including frequency and user filters, to analyze adoption over a specified date range.

Instructions

Get MCP (Model Context Protocol) tool usage: which MCP servers and tools are being used, 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_mcp_usage"
  }
}

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 must fully disclose behavioral traits. It only states it retrieves usage data but does not mention read-only nature, side effects, authorization needs, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with the key action front-loaded. Very concise, but could be slightly more structured to include parameter context.

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?

While the description explains the output, it does not mention the available filter parameters (users, date range) nor provide any hint about the response structure, which is missing an output schema.

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 parameter-specific information beyond what the schema already provides.

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' and the resource 'MCP tool usage', specifying the exact information returned (which servers, tools, and frequency). This effectively distinguishes it from sibling tools like get_model_usage or get_daily_usage.

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?

The description provides no guidance on when to use this tool versus alternatives such as get_model_usage or get_daily_usage. There are no exclusions, contexts, or comparisons given.

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