Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

mailpool_account

Mailpool workspace: subscription slots and warmup.

Ops:

  • slots — mailboxes used vs paid, per type, and warmup slots. A new mailbox needs a free slot (buying slots is not served here).

  • warmup — inboxes enrolled in Mailpool warmup, with status.

  • warmup_inbox — one enrolled inbox (warmup_id): settings, counters.

  • warmup_available — active mailboxes not enrolled yet.

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": "mailpool_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNowhat to read.slots
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
limitNopage size, 1-100.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
offsetNoitems to skip.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
warmup_idNowarmup inbox id (op="warmup_inbox").

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. All four ops are described as reads (counts, statuses, settings), which implicitly conveys safety, but it does not state read-only intent, pagination behavior for limit/offset, or return shape.

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 front-loaded with a one-line scope statement and then a compact per-op list. It is efficient, though the ops block could be slightly tighter.

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?

For a 9-parameter tool with no annotations and no output schema, the description covers the core operations and their returned concepts. It leaves out pagination behavior and does not explain the common scope parameters (`_org`, `_group`, `_project`, etc.), relying entirely on the schema for those.

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 description coverage is 100%, so the baseline is 3. The description adds meaning by explaining what each `op` enum value returns (slot counts, warmup enrollment status, inbox settings/counters) and ties `warmup_id` to `warmup_inbox`, going beyond the schema's terse "what to read."

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 names the resource (Mailpool workspace subscription slots and warmup) and enumerates four specific read operations. It is clearly distinct from mailbox/domain management siblings, though it never explicitly contrasts itself with them.

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?

It gives one useful exclusion (buying slots is not served here) and implies that `warmup_available` is for finding mailboxes to enroll. However, it does not explicitly say when to choose each op versus an alternative or when this tool should not be used.

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

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