Skip to main content
Glama

get_quota_status

Track session-local YouTube Data API quota usage by tool and endpoint, showing units spent and layers used to compare against the 10,000/day free tier per key without an API call.

Instructions

Session quota ledger: units spent per tool and per endpoint, layers used.

No API call, 0 units. The Data API does not expose remaining quota, so this
is a session-local tally against the 10,000/day free tier per key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does well: it discloses that the call costs zero units and makes no network request, and critically that the Data API does not expose remaining quota, so the number is a session-local tally rather than an authoritative figure. The reference to the 10,000/day free tier per key gives the agent the baseline to interpret the ledger against.

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 short sentences, front-loaded with what the tool returns and immediately followed by the cost and the caveat. 'Layers used' is the one phrase that does not earn its place because it is never defined.

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?

An output schema exists, so return values need not be described. The description covers the essentials for a zero-parameter diagnostic: cost, scope, and the trustworthiness limit of the tally. Only minor gaps remain, such as when the session is considered to start or reset.

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 zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description adds no parameter noise.

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 names the specific resource and its contents: a session quota ledger showing units spent per tool and per endpoint. That is concrete enough to separate it from the search/retrieval siblings, though 'layers used' is unexplained jargon that slightly muddies the stated scope.

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?

Usage is implied rather than stated: an agent can infer it should call this to check its spend, and 'No API call, 0 units' tells it the call is free. There is no explicit when-to-use guidance, no mention of how often to check, and no named alternative for authoritative quota data.

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