Skip to main content
Glama
Sign In
SmartBear MCP server

SmartBear MCP server

Official
by SmartBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

QMetry: Fetch API Call Quota

qmetry_fetch_api_call_quota
Read-onlyIdempotent

Fetch QMetry API call limits, consumed and remaining calls, and reset times to check quota before large batches or diagnose rate-limit errors.

Instructions

Fetch the hourly and daily QMetry Open API call limits, calls consumed, calls remaining, and reset times

Toolset: Projects

Parameters:

  • projectKey (string): Project key - unique identifier for the project (default: "default")

Output Description: JSON object: limitEnabled (boolean), hourly and daily objects each with limit, consumed, remaining (numbers) and resetsAt (UTC timestamp), and serverTime (UTC timestamp)

Use Cases: 1. Check how many API calls remain before running a large batch of operations 2. Diagnose rate-limit or quota-exceeded errors returned by other QMetry tools 3. Find out when the hourly or daily quota will reset 4. Confirm whether API call limits are enabled for the instance

Examples:

  1. Check the current API call quota

{}

Expected Output: limitEnabled flag, hourly and daily { limit, consumed, remaining, resetsAt }, and serverTime

Hints: 1. No parameters are needed — the quota belongs to the account/API key, not to a project 2. Calling this tool is free: it does not consume hourly or daily quota 3. If limitEnabled is false, no API call limits are enforced and the counts are informational only 4. resetsAt and serverTime are UTC ISO-8601 timestamps — compare resetsAt with serverTime, not with local time, to compute time until reset 5. Before a large batch of create/update/link calls, check hourly.remaining and daily.remaining and warn the user if the batch would exceed them 6. If another QMetry tool fails with a rate-limit or quota error, call this tool to report remaining calls and the reset time

Input Schema

NameRequiredDescriptionDefault
projectKeyNoProject key - unique identifier for the projectdefault

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.43.0

TDQS

A4.7/5.0
Behavior5/5

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

The description goes beyond the read-only and idempotent annotations. It says calling the tool consumes no quota, the quota belongs to the account or API key rather than a project, and limitEnabled=false means counts are only informational. It also says timestamps are UTC ISO-8601 and should be compared against serverTime.

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

Conciseness3/5

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

The sections are well organized and front-loaded. However, the parameters section repeats the schema, the expected output in the example repeats the output description, and the use cases overlap with hints 5 and 6.

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

Completeness5/5

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

There is no output schema, so the description documents the full response structure and field types. It also explains how to interpret the fields, which leaves nothing missing for a simple diagnostic 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?

Schema coverage is 100%, but the schema implies projectKey matters. The description clarifies that no parameters are needed because quota is not project-scoped. However, it contradicts itself by listing projectKey as a parameter while saying none are needed.

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 says the tool fetches the hourly and daily QMetry Open API call limits, consumed, remaining and reset times. That is a specific verb plus resource. No sibling does quota checking, so it is clearly distinct.

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

Usage Guidelines5/5

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

The use cases and hints say when to call it: before large batches of create/update/link calls, and after rate-limit errors from other QMetry tools. They also tell the agent how to act on the result, such as warning the user if a batch would exceed the remaining quota.

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