Skip to main content
Glama

NewsletterProAI

newsletter_draft

Destructive

Returns a subject line and HTML body written from your topic and notes. Needs a write-scoped key; each call is metered. Pricing: {"unit": "call", "price_usd": null, "pricing_url": "https://newsletterproai.eliteaiempire.com/pricing", "free_quota": 0, "per_key_daily_cap": 25, "note": "Needs a scoped API key. The per-call price is not published yet; keys are issued on request."}.

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": {
      "confirm": "<confirm>",
      "notes": "<notes>",
      "topic": "<topic>"
    },
    "name": "newsletter_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesYes
topicYes
confirmYesMust be true. This action is paid or destructive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent, and the description adds real value on top: write-scoped auth requirement, per-call metering, zero free quota, and a 25/day per-key cap. What it does not explain is why a text-generation tool is flagged destructive or what side effects justify the 'confirm' gate — the schema hints at 'paid or destructive' but the description stays silent on the destructive dimension.

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 one-sentence purpose statement is front-loaded and waste-free. The trailing embedded pricing JSON is dense and precise but stylistically odd inside a description, and it duplicates itself ('price_usd': null paired with a note saying the price is unpublished).

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

Completeness3/5

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

For a 3-required-parameter, no-output-schema tool, the description covers cost, quota, rate limit, auth scope, and return shape well enough to call it safely. It is incomplete on the two substantive inputs (topic, notes) and on the destructive/confirm semantics, which is the main remaining gap.

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 coverage is only 33% — only 'confirm' is documented (as a paid/destructive gate). The description gestures at 'topic' and 'notes' as generation inputs but adds no real semantics (length, format, tone, what belongs in notes), and never mentions the required 'confirm' parameter even though it is the one gating a paid, destructive action.

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?

The description gives a specific verb and output ('Returns a subject line and HTML body') plus the input basis ('written from your topic and notes'), which tells an agent exactly what the tool produces. It doesn't need to name siblings because about/pricing/usage are obviously different functions, but it never explicitly distinguishes itself either.

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 line 'Needs a write-scoped key; each call is metered' implies a cost-gated, deliberate-use operation, which is useful implied guidance. However, there is no explicit when-to-call-this-vs-something-else statement and no statement of when not to call it, so the agent must infer the usage conditions.

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.

Resources