Skip to main content
Glama
MrNewDelhi

Mailosaur MCP

by MrNewDelhi

mailosaur_usage_transactions

Retrieve recent transaction usage for your Mailosaur account using an account-level API key.

Instructions

Retrieve recent transaction usage. Requires an account-level API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:492-500 (registration)
    Tool 'mailosaur_usage_transactions' is registered via server.tool() with an empty schema and an async handler that calls mailosaur.usage.transactions().
    server.tool(
      "mailosaur_usage_transactions",
      "Retrieve recent transaction usage. Requires an account-level API key.",
      {},
      async () => {
        const result = await mailosaur.usage.transactions();
        return response(result);
      }
    );
  • The handler logic for mailosaur_usage_transactions is the inline async arrow function that calls mailosaur.usage.transactions() and returns the result via the response() helper.
    async () => {
      const result = await mailosaur.usage.transactions();
      return response(result);
    }
  • The response() helper function used by the handler to format the return value as MCP content with JSON-stringified text.
    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?

With no annotations, the description fails to disclose behavioral traits such as idempotency, pagination, or the meaning of 'usage'. It only states it retrieves usage, which is insufficient.

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 with no wasted words. It is concise and front-loaded.

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 0 parameters and no output schema, the description is somewhat incomplete; it does not define 'recent' or what the usage data includes, leaving the agent with limited context.

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, so the description need not add parameter info. Baseline is 4 per instructions, and the description adds authentication context beyond the schema.

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 verb 'retrieve' and the resource 'recent transaction usage', distinguishing it from siblings like mailosaur_usage_limits which likely retrieves limits. However, it is somewhat terse.

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 provides a prerequisite (requires an account-level API key) but does not offer guidance on when to use this tool versus alternatives like mailosaur_usage_limits.

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