Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Check Email Daily Usage

check_email_daily_usage
Read-only

Call this before queuing bulk email outreach — the mailboxes list tells you which mailboxes still have headroom today. Each connected mailbox has its own daily cap (Gmail/Outlook score reputation per from address, not per Sliq user). An empty mailboxes list means no email account is connected — tell the user to connect a Gmail or Outlook mailbox in Settings. { 'emails': { 'mailboxes': [ {'email': str, 'provider': str, 'sent_today': int, 'daily_limit': int, 'remaining_today': int, 'is_default': bool}, ... ], }, 'queue': { 'pending': int, 'pending_approval': int, 'sent_total': int, 'failed': int, 'next_send': str, # optional }, }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
on_behalf_ofNoAn agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / on_behalf_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

While the annotation confirms it is read-only, the description adds crucial behavioral context by clarifying *how* the usage is calculated: 'Gmail/Outlook score reputation per `from` address, not per Sliq user.' This is vital information that goes beyond the simple 'read-only' hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is highly focused, starting with a clear summary. While the inclusion of the full return schema makes it long, the explanatory text is efficient and minimizes fluff.

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

Completeness5/5

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

The definition is extremely complete. It outlines the purpose, the optimal usage timing, the meaning of the input parameter, and provides a fully structured expectation of the complex return data (both email status and queue status).

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?

Although schema coverage is 100%, the description provides excellent semantic context for the `on_behalf_of` parameter, explaining that it applies to the agent's 'agency client's email' and affects their 'agents, settings, connected accounts, and credits.' This clarifies the real-world scope of the input.

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 clearly states the specific function: checking per-mailbox email outreach usage limits and queue status. This distinguishes it from other potential reporting or queue management tools in the list.

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

Usage Guidelines5/5

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

It provides explicit instructions on when to call the tool ('Call this before queuing bulk email outreach'). Furthermore, it details the necessary user action if the tool returns an empty list of mailboxes, preventing immediate failure.

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

All Sliq toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources