Skip to main content
Glama
ThinAirTelematics

ThinAir Data

Official

quota

View your API usage, daily limit, and plan name. Manage resource consumption and explore upgrade options for the database AI assistant.

Instructions

Check current API usage, daily limit, plan name, and upgrade options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • bin/server.js:76-81 (registration)
    Registration of the 'quota' tool in the TOOLS array. It is listed under the DISCOVER tier (free). It has no inputSchema beyond { type: 'object' }, meaning no required inputs. The handler for CallToolRequestSchema (line 190-193) simply returns a redirect message pointing to the hosted MCP server, as this file is a static local adapter.
    {
      name: "quota",
      description:
        "Check current API usage, daily limit, plan name, and upgrade options.",
      inputSchema: { type: "object" },
    },
  • Generic catch-all handler for all tool calls (including 'quota'). It does not execute the tool logic locally; instead it returns a redirect message telling the user to use the hosted MCP server at https://data.thinair.co/mcp.
    server.setRequestHandler(CallToolRequestSchema, async () => ({
      content: [{ type: "text", text: REDIRECT_MESSAGE }],
      isError: false,
    }));
Behavior3/5

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

Without annotations, the description carries the burden. 'Check' implies a read-only operation, but it does not explicitly state safety, authentication needs, or rate limits. The behavior is partially transparent but could be more explicit.

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?

A single sentence that is front-loaded with the action and resource. Every word earns its place, and there is no redundancy or unnecessary detail.

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?

Given the simplicity of the tool (no parameters, no output schema), the description adequately covers the main return fields. It is sufficient for an agent to understand what the tool does and what it returns.

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?

There are no parameters, and schema coverage is 100%. The description adds meaning by listing the return values (usage, limit, plan, upgrade options), which is helpful beyond the empty schema.

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 uses a specific verb 'Check' and clearly identifies the resource: API usage, daily limit, plan name, and upgrade options. It is easily distinguishable from sibling tools which focus on database 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?

No guidance is provided on when to use this tool versus alternatives. It does not mention exclusions or context, leaving the agent to infer usage from the title alone.

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/ThinAirTelematics/thinair-data'

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