Skip to main content
Glama

Read displayed ZCode quota

zcode_quota
Read-onlyIdempotent

Reads the remaining quota percentages shown in the ZCode UI on demand, briefly opening the context popover to capture usage windows. Use it to check current quota levels without pressing reset or reading credentials.

Instructions

Read the remaining quota percentages displayed by the official ZCode UI on demand. May be cached; account and provider cannot be verified, reset times are display text, and missing windows mean unknown. Temporarily opens and closes the context popover; never presses reset or reads credentials.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish the safe read profile (readOnly, idempotent, non-destructive), yet the description still adds real value: caching, unverifiable account/provider, reset times being display text, and missing windows meaning unknown. It also discloses a side effect not visible in annotations — temporarily opening and closing the context popover — and explicitly rules out resetting or credential access.

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?

Two sentences, front-loaded with the core action, followed by a dense caveat block where each clause carries distinct information. The caveat sentence is telegraphic and slightly comma-spliced, but no clause is filler.

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?

With no output schema, the description does useful work by describing the returned content (remaining quota percentages, windows that may be absent) and its reliability limits. It does not specify the response shape beyond 'percentages', which is a minor gap for a zero-parameter tool.

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 takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not waste words restating an empty schema.

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 a specific verb and resource ('read the remaining quota percentages') plus the authoritative source ('displayed by the official ZCode UI'), which implicitly separates it from the swarm_quota sibling. It stops short of naming an alternative outright, so the differentiation is inferred rather than explicit.

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?

'On demand' signals this is a pull-style check rather than an event stream, and the caching caveat hints at freshness limits. However, there is no explicit when-to-use versus when-to-prefer-alternatives guidance, and no statement of how often it is reasonable to call.

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