Skip to main content
Glama
Sign In

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. max_daily_sends is the mailbox's user-set cap, which the user changes on the Integrations page; daily_limit is today's effective cap, which is lower while the mailbox is still warming up. { 'emails': { 'mailboxes': [ {'email': str, 'provider': str, 'sent_today': int, 'daily_limit': int, 'max_daily_sends': int, 'remaining_today': int, 'is_default': bool}, ... ], }, 'queue': { 'pending': int, 'pending_approval': int, 'sent_total': int, 'failed': int, 'next_send': str, # optional }, }

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_email_daily_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
on_behalf_ofNoA teammate's email, or an agency client's from list_agency_clients, to run this call in that 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
    • changedInput schema / properties / on_behalf_of / description
      Previous value: -"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."New value: +"A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
  2. 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."
+}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description goes well beyond that, explaining that Gmail/Outlook reputation is scored per `from` address rather than per Sliq user, that `daily_limit` can be below `max_daily_sends` during warmup, and that an empty list means no mailbox connected. These are real behavioral constraints an agent cannot get from the schema.

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 summary leads with the core purpose and the usage instruction, followed by field-level semantics. The <returns> block is lengthy but earns its place because no output schema exists, though the field-by-field layout is more verbose than strictly needed.

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?

With no output schema, the description supplies the full return shape (mailboxes array fields plus queue counters and optional next_send) and explains the distinction between user-set and warming-up caps. An agent has everything it needs to call the tool and interpret the response.

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 single `on_behalf_of` parameter has full schema description coverage, so the baseline of 3 applies; the description never mentions acting on behalf of a teammate or agency client, adding no meaning beyond the 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?

States a specific verb and resource ('Check per-mailbox email outreach usage limits and queue status') and scopes it to per-mailbox caps, which separates it from account-level siblings like get_credit_usage and from queue-mutating tools like queue_email_outreach.

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

Usage Guidelines4/5

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

Explicitly says when to call it ('before queuing bulk email outreach') and what the output means for that decision, plus a fallback instruction when the mailboxes list is empty. It does not name the alternative tools (e.g. get_mailbox_deliverability, check_linkedin_daily_usage) for adjacent questions, so the routing is clear but not exhaustive.

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