Skip to main content
Glama

tosea_get_quota_status

Check quota usage for ToseaAI presentation features to monitor available resources and plan document-to-presentation workflows.

Instructions

Inspect quota status for all features or a single feature key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feature_keyNo

Implementation Reference

  • Registration and handler definition for tosea_get_quota_status tool in src/tools.ts. The handler delegates to the ToseaClient's getQuotaStatus method.
    server.tool(
      "tosea_get_quota_status",
      "Inspect quota status for all features or a single feature key.",
      { feature_key: z.string().min(1).optional() },
      async ({ feature_key }) => {
        try {
          return asToolResult(await client.getQuotaStatus(feature_key));
        } catch (error) {
          throw wrapToolError(error);
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'inspect' which suggests a read-only operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or what the output looks like. For a quota tool, it should ideally mention if it returns real-time data, historical usage, or limits.

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 description is a single, efficient sentence that front-loads the purpose and scope. Every word earns its place with no redundancy or unnecessary details, making it easy to parse quickly.

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

Completeness3/5

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

Given the tool's low complexity (1 optional parameter, no output schema, no annotations), the description is minimally complete. It covers the basic purpose and parameter usage but lacks details on output format, error handling, or integration context that would be helpful for an agent to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning by explaining that 'feature_key' is optional and used to inspect a single feature, while omitting it returns status for all features. However, with 0% schema description coverage and only 1 parameter, this is adequate but not comprehensive. It doesn't specify what valid feature keys are or provide examples.

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 clearly states the action ('Inspect') and resource ('quota status'), specifying scope ('for all features or a single feature key'). It distinguishes from siblings by focusing on quota inspection rather than editing, exporting, or listing operations. However, it doesn't explicitly differentiate from 'tosea_get_permissions_summary' or 'tosea_get_presentation_full_data' which are also read operations.

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

Usage Guidelines2/5

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

The description implies usage for checking quota status but provides no explicit guidance on when to use this tool versus alternatives. There's no mention of prerequisites, typical use cases, or comparison with sibling tools like 'tosea_get_permissions_summary' that might overlap in monitoring contexts.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ToseaAI/mcp-ToseaAI'

If you have feedback or need assistance with the MCP directory API, please join our Discord server