Skip to main content
Glama
Sign In

Groundbase

by com.groundbasecrm.mcp
OverviewDiscussionsAdmin

Sending settings

sending_settings

Daily cap on campaign EMAILS (not SMS) per day in the account timezone. get: cap, sent_today, remaining_today, domain_caps. set: daily_email_send_cap (null = none, 0 = stop today), account-wide or, with domain, for one domain inside it. Over-cap recipients wait for later days. Use to warm a new domain (~20/day).

Input Schema

NameRequiredDescriptionDefault
actionYes
domainNoset: bare hostname, e.g. 'example.com'. Omit for the account-wide cap.
daily_email_send_capNoset: non-negative integer or null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / action / description
      Removed value: -"'get' to read, 'set' to write."
    • changedInput schema / properties / daily_email_send_cap / description
      Previous value: -"For action='set'. Non-negative integer, or null to remove the cap entirely."New value: +"set: non-negative integer or null."
    • changedInput schema / properties / domain / description
      Previous value: -"For action='set'. Bare hostname, e.g. 'example.com'. Caps only mail sent from that domain, inside the account-wide cap. Omit to set the account-wide cap, which totals every domain and is the only cap on a domain without its own."New value: +"set: bare hostname, e.g. 'example.com'. Omit for the account-wide cap."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the effect of null (none) and 0 (stop today), account-wide versus per-domain scoping, and that over-cap recipients wait for later days. It does not discuss permissions or idempotency nuances, but the key behavioral consequences are covered.

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 front-loaded with the core constraint and then packs get/set semantics into a compact line. Every clause carries useful information with no filler.

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?

With no output schema, the description still explains what get returns and what set affects, including domain-level behavior. It is nearly complete for a small dual-action settings tool, with only minor auth/permission context missing.

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?

Schema coverage is 67%, and the description compensates well by explaining action outcomes, domain scoping, and the null/0 semantics for daily_email_send_cap. It adds meaningful interpretation beyond the structured fields.

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 states a specific resource (daily cap on campaign EMAILS) and operation (get/set), explicitly excluding SMS. It also names the exact fields returned by get and the value written by set, so an agent can distinguish it from siblings like sms_manage or email_send.

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?

It gives a clear use case (warming a new domain at roughly 20/day) and explains get versus set behavior. It does not enumerate alternatives beyond excluding SMS, but the context is strong enough to guide selection.

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

All Groundbase 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