Skip to main content
Glama

AIClipMaker.org

Get plan and remaining minutes

get_quota
Read-onlyIdempotent

The authenticated user's plan and remaining processing minutes. Call before large jobs; process_video fails with quota_exceeded when the balance is insufficient.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, non-destructive, closed-world call, so the safety profile is covered. The description adds value beyond them by disclosing the failure semantics of the dependent tool and the fact that this is a precondition check rather than a job action.

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?

Two short sentences, front-loaded with what is returned and followed immediately by the actionable guidance. Every clause carries information; no filler or restatement of the title beyond the return value itself.

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?

For a zero-parameter tool with no output schema, the description covers what is returned (plan, remaining minutes) and why it matters. It stops short of indicating format or units for the remaining-minutes value, which would fully close the gap left by the absent output schema.

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 applies. Nothing in the description misleads about inputs, and it correctly implies the call is scoped by authentication alone.

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 exact resource returned: the authenticated user's plan and remaining processing minutes, scoped explicitly to the calling user. It is clearly distinct from siblings like process_video, list_clips, or get_job_status, though it uses a noun phrase rather than a verb.

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

Usage Guidelines4/5

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

It states a concrete trigger ('Call before large jobs') and ties it to a named sibling failure mode ('process_video fails with quota_exceeded when the balance is insufficient'). No explicit when-not-to-use case is given, but the context is strong enough for correct tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources