Skip to main content
Glama
SunLicense MCP server

SunLicense MCP server

Official

mcp_usage

Read-onlyIdempotent

Check how many SunLicense MCP tool calls your organization has used today and how many remain, without counting the check itself. Use it to monitor daily usage or confirm no cap applies.

Instructions

How many SunLicense MCP tool calls the organization has used today and how many are left (limit null: no daily cap). This check itself doesn't count.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
leftNo
planYes
usedYes
limitYesnull: no daily cap
resetsAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish safe read-only, idempotent behavior, and the description adds useful context: this check itself does not count, and a null limit means no daily cap. It does not describe auth or response shape, though an output schema is present.

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 definition is compact and front-loads the primary counts before the useful parenthetical caveat. Every clause earns its place, including the quota-exclusion note.

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

Completeness4/5

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

Given zero parameters and an output schema, the description supplies the key operational quirk that the check itself does not count and explains null limit semantics. It omits explicit usage routing, but for this simple quota probe it is largely complete.

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?

There are zero input parameters, so the baseline is 4. The description adds no parameter semantics because none exist.

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?

States it reports today's MCP tool call usage and remaining allowance, with a null limit meaning no daily cap. This is a specific measure and resource, though it does not explicitly contrast with related analytics or licensing-stat tools.

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?

The implied use is checking current daily call consumption or quota, but the description gives no explicit when-to-use guidance or alternatives. It is adequate for an obvious quota probe but leaves routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.