Skip to main content
Glama
Quolle MCP

Quolle MCP

by Quolle-main

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
QUOLLE_API_KEYYesYour Quolle API key (starts with qle_). Required.
QUOLLE_BASE_URLNoOptional base URL for the Quolle API. Defaults to https://api.quolle.com.https://api.quolle.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
send_emailA

Send one transactional email (OTP, receipt, notification, verification). Provide html with subject, or a template slug with variables. The from domain must be verified. Pass an idempotencyKey (e.g. the order or user id plus purpose) so that if you retry, the email is not sent twice.

send_batchA

Send up to 100 emails in one all-or-nothing request (no attachments in a batch). Each item takes the same fields as send_email.

get_emailA

Look up one email by id: status (queued, sent, delivered, bounced, complained, failed…) and open/click counts.

list_emailsA

List recent sends, newest first, optionally filtered by status or recipient. Needs a full-access API key.

cancel_emailA

Cancel a scheduled email that has not been sent yet.

list_domainsA

List the account's sending domains and whether each is verified. Use it to pick a valid from before sending. Needs a full-access API key.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 6 tools

Disambiguation5/5

Each tool maps to a distinct resource and action: sending (single vs. batch is clearly delimited by the 100-email, all-or-nothing description), lookup by id vs. listing, cancellation, and domain listing. No two tools could plausibly be chosen for the same intent.

Naming Consistency5/5

All six tools follow a strict verb_noun snake_case pattern (send_email, send_batch, get_email, list_emails, list_domains, cancel_email). Verb choices are standard CRUD-style and predictable.

Tool Count5/5

Six tools is well within the ideal 3-15 range and each earns its place in a transactional email workflow (send, batch send, cancel, inspect, list, validate sender domain). Nothing looks like padding or a leftover utility.

Completeness3/5

Core send/read/cancel flow is covered, but cancel_email implies scheduled sends exist while no tool lets an agent schedule one, and domain verification/creation and template discovery or management are absent even though send_email accepts template slugs. These are meaningful gaps an agent would hit in real workflows.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues