Skip to main content
Glama
Sign In

ShockAtlas

by com.shockatlas
OverviewDiscussionsAdmin

Subscribe an address to the free weekly

subscribe_newsletter
Idempotent

Asks the free weekly edition for one email address. The address receives a single confirmation link and nothing else until its owner clicks it (double opt-in); one request per address per hour. Call it only for a person who asked to receive the editions, and say so with consent: true. The paid plan cannot be subscribed here: get_offers.premium.subscribe_url is where a person signs in and subscribes.

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>",
      "consent": "<consent>"
    },
    "name": "subscribe_newsletter"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe address of the person who asked for the free weekly
consentYestrue: the owner of this address asked for the editions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (write operation, idempotent, non-destructive, closed-world), the description discloses the double opt-in flow — the address receives a single confirmation link and nothing else until it is clicked — plus a concrete rate limit of one request per address per hour. These are exactly the side effects and limits an agent needs before performing the write.

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

Conciseness4/5

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

It is short and front-loaded: purpose, behavioral consequence, usage precondition, then the exclusion/alternative. The opening sentence is the weakest link, since 'asks the free weekly edition for one email address' takes a re-read, but no sentence is wasted.

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 two-parameter write tool with no output schema, the definition covers the consequential behavior (confirmation link, nothing sent before opt-in), throttling, and the consent requirement. The only missing piece is what the call itself returns on success, which is a minor gap given the described email-side outcome.

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%, so both parameters are already documented in the schema, including the const-true constraint on consent. The description reinforces the rationale for consent (the owner asked for the editions) and adds the per-address throttling, but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 states a specific resource ('the free weekly edition') and the action applied to it ('asks ... for one email address', i.e. subscribing), and it explicitly excludes the paid plan by pointing to get_offers.premium.subscribe_url. The verb phrasing 'asks the free weekly edition for' is slightly unusual, but combined with the title the intent is unambiguous.

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

Usage Guidelines5/5

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

It gives an explicit precondition ('only for a person who asked to receive the editions'), a required flag ('say so with consent: true'), and a clear exclusion with the alternative route for paid subscriptions. An agent knows both when to call it and where to send a paid-plan request instead.

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

All ShockAtlas toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources