Skip to main content
Glama

Send Email

chat

Send emails from natural language prompts. Hosted at https://cloudish.ai.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNo
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / chat_id / default
      Added value: +""
    • removedInput schema / properties / chat_id / description
      Removed value: -"Continue an existing conversation. Omit to start a new one; the reply includes the id."
    • addedInput schema / properties / chat_id / title
      Added value: +"Chat Id"
    • removedInput schema / properties / message / description
      Removed value: -"The message to send to the agent."
    • addedInput schema / properties / message / title
      Added value: +"Message"
    • addedInput schema / title
      Added value: +"chatArguments"
  2. First observed

TDQS

C2.2/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about immediacy, irreversibility, sending account, or confirmation. For an action that presumably dispatches real email from a user's identity, the only extra information offered is the hosting URL, which is not behaviorally relevant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in a single short sentence, which is good, but the second sentence ('Hosted at https://cloudish.ai.') is vendor boilerplate that consumes space without helping an agent decide or invoke. The result is brief yet under-specified rather than efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and two undocumented parameters, the description should establish side effects, auth/account context, and return behavior, and it establishes none of them. An agent cannot safely predict what happens after invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does not: it never explains whether 'message' is the raw email body or an instruction to an LLM, nor what 'chat_id' (empty default) scopes or threads. The one hint — natural language — is ambiguous and arguably conflicts with a field literally named 'message'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Send emails from natural language prompts" does give a verb and resource, but the tool is named 'chat' with a 'message'/'chat_id' schema, so the description contradicts the name's implied chat semantics without resolving it. It never clarifies whether the natural-language prompt is composed into an email, sent immediately, or returned as a draft, leaving the actual operation vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no indication of what to do instead for plain conversation versus actual email delivery. The agent is left to infer the trigger condition for calling this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.