Skip to main content
Glama

COTAL actions (cotal.ai)

Subscribe to Cotal updates

cotal_subscribe_newsletter
Idempotent

Subscribes the user's email to release updates from the Cotal team. Idempotent: an already-subscribed email is a no-op.

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": {
      "email": "<email>"
    },
    "name": "cotal_subscribe_newsletter"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe user's email address. Required so the record has a traceable origin.
sandboxNoDry run: validate the call, apply rate limits, store nothing. Use it to test the integration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the restated no-op behavior partly duplicates structured data. It adds no information on authentication expectations, whether the user is confirmed/consenting, or what a successful call returns.

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?

Two short sentences, zero filler, with the core action front-loaded and the idempotency caveat as the second beat. Nothing could be removed without losing meaning.

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

Completeness4/5

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

For a low-complexity two-parameter tool with no output schema and complete schema coverage, the description plus annotations cover action, scope, and repetition behavior adequately. A brief note on the success response and whose account is subscribed would close the remaining gap.

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 description coverage is 100%, and both the email format and the sandbox dry-run flag are fully documented in the schema, including the rate-limit-validate-store-nothing semantics. The description adds nothing beyond that, so baseline 3 applies.

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?

States a specific verb and resource ('Subscribes the user's email to release updates from the Cotal team'), so intent is unmistakable. It does not differentiate from the nearest sibling, cotal_join_waitlist, which is a related but distinct signup path.

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?

The phrase 'release updates from the Cotal team' implies when the tool applies, but there is no explicit when-to-use or when-not guidance, and no pointer to cotal_join_waitlist for the adjacent signup case. Usage must be inferred from the name and scope.

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.