Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_usage_limits

Retrieve current account usage limits to monitor remaining quota and prevent service interruptions.

Instructions

Retrieve account usage limits. Requires an account-level API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:482-490 (registration)
    Registration of the 'mailosaur_usage_limits' tool via server.tool(), with handler logic inline calling mailosaur.usage.limits().
    server.tool(
      "mailosaur_usage_limits",
      "Retrieve account usage limits. Requires an account-level API key.",
      {},
      async () => {
        const result = await mailosaur.usage.limits();
        return response(result);
      }
    );
  • Handler function for the tool - calls mailosaur.usage.limits() and wraps the result in a text response.
    async () => {
      const result = await mailosaur.usage.limits();
      return response(result);
    }
  • Empty schema - the tool has no input parameters.
    {},
  • Helper function that wraps a value into the MCP text response format (JSON.stringify'd).
    function response(value: unknown) {
      return {
        content: [
          {
            type: "text" as const,
            text: JSON.stringify(value, null, 2)
          }
        ]
      };
    }
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only indicates that the tool is a read operation ('Retrieve') and states the auth requirement, but lacks details on rate limits, data returned, or any side effects. This is insufficient for a tool without annotations.

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 two sentences: the first states the purpose, the second adds an auth requirement. Every word is necessary, and the key information is front-loaded. No wasted content.

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

Completeness2/5

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

The tool has no output schema, so the description should explain what the tool returns. It fails to do so, only stating it retrieves limits without describing the format or content. Additionally, no behavioral constraints or edge cases are mentioned, leaving significant gaps.

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 input schema has no parameters, so schema coverage is 100% by default. The description does not need to explain parameters, and no additional semantic detail is possible. Baseline score of 3 is appropriate.

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 explicitly states the verb 'Retrieve' and the resource 'account usage limits', making the purpose clear. However, it does not differentiate from the sibling tool 'mailosaur_usage_transactions', which could be related, but the purpose is distinct enough.

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?

The description mentions that an account-level API key is required, providing a prerequisite for use. However, it offers no guidance on when to use this tool versus alternatives like 'mailosaur_usage_transactions', leaving usage context implied.

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/MrNewDelhi/mailosaur-mcp'

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