Skip to main content
Glama
Quolle MCP

Quolle MCP

by Quolle-main

List sending domains

list_domains
Read-only

Lists your account's sending domains and shows whether each is verified, so you can choose a valid from address before sending email. Requires a full-access API key.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds genuinely new behavioral context beyond the annotations: the authentication requirement (full-access API key) and the fact that verification status is part of the payload. Return format, ordering, and any rate limits are not described, but the added auth constraint is the main gap filler for a no-parameter read.

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?

Three short sentences, each doing distinct work: what it returns, when to call it, and what it requires. The purpose is front-loaded and no sentence repeats the title or the annotations.

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?

For a zero-parameter read with annotations covering safety and no output schema, the description supplies the three things an agent cannot infer: the payload includes verification status, the intended use (choosing a `from`), and the full-access key prerequisite. Nothing needed to call it correctly is 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?

The tool takes zero parameters, so the baseline is 4 and there is nothing further the description could usefully say about inputs. It correctly implies the listing is scoped to the account behind the API key rather than requiring a filter argument.

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 (list) and resource (sending domains) plus the returned attribute (verified status), so the agent knows exactly what it gets back. No sibling (send_email, get_email, list_emails, cancel_email, send_batch) touches domains, and the description makes the domain-level scope unambiguous.

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?

"Use it to pick a valid `from` before sending" gives a concrete trigger and implicitly routes the agent here before send_email/send_batch. It stops short of explicit when-not conditions (e.g., that this is unnecessary if the from address is already known), so it is clear context without full alternatives coverage.

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