Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List email configurations

list_email_configurations
Read-only

List a workspace's email configurations with IDs, names, providers, senders and active flags. Use the returned ID as a form's emailConfigurationId in create_form or update_form.

Instructions

List the workspace's email configurations: id, name, slug, description, provider, sender, default and active flags, and how many recipients each has. Pass an id as a form's emailConfigurationId in create_form or update_form. API keys, SMTP and Mailgun settings and recipient addresses are never returned here.

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_email_configurations"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeInactiveNoAlso return inactive configurations. Only an active one sends email, so leave this off when choosing one for a form.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful disclosure beyond that: sensitive fields (API keys, SMTP/Mailgun settings, recipient addresses) are never returned, which tells the agent what it can and cannot rely on. It does not describe pagination or ordering, which keeps it from a 5.

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 tight sentences: what it lists, how the output is consumed, and what is withheld. The field enumeration is front-loaded and every clause carries information.

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?

There is no output schema, so the description compensates by enumerating the returned fields and stating which sensitive values are excluded. Combined with the annotation safety profile and full parameter coverage, an agent has everything needed to call it and use the result correctly.

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?

Schema coverage is 100% and the single parameter (includeInactive) already has a full description explaining the active-only sending behavior. The tool description adds no further parameter semantics, so the baseline 3 applies.

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 ("List the workspace's email configurations") and immediately enumerates the returned fields (id, name, slug, provider, sender, default/active flags, recipient count), which no sibling does. An agent can tell this apart from list_forms or list_webhooks without opening the schema.

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 routes downstream usage: "Pass an `id` as a form's `emailConfigurationId` in create_form or update_form," which links to two named siblings. It lacks an explicit when-not-to-use statement (e.g. pointing at another tool for creating configurations), but the context is clear.

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

Deploy Server

Other Tools