Skip to main content
Glama

The world according to capital

Subscribe to the newsletter

subscribe_to_newsletter

Subscribe an email address to The world according to capital, Tiago's newsletter: the companies VCs just backed, hand-picked by Tiago. Five minutes, every weekday. Call it only with an address its owner asked you to sign up. It sends that address a confirmation link, and the subscription starts only when its owner clicks it (double opt-in), so tell them to look for the email from Tiago Martins. The answer is the same whether or not the address was already on the list. The RSS feed at https://www.notacompany.com/archive/rss needs no email at all.

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": "subscribe_to_newsletter"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe address to send the confirmation link to, given by its owner.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations it discloses the full downstream behavior: a confirmation link is sent, the subscription only activates on click (double opt-in), the sender name the recipient should look for, and that the response is identical whether or not the address was already subscribed. That response-uniformity note is what makes the non-idempotent hint interpretable rather than a trap.

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?

Front-loaded with the action, then the consent rule, then the opt-in mechanics, then the alternative — a sensible order. The newsletter blurb ('Five minutes, every weekday') is marketing copy that does little for an agent, a small amount of waste in an otherwise tight paragraph.

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 one-parameter, no-output-schema tool it covers consent, opt-in flow, caller-facing messaging, and the email-free alternative. It stops short of describing error handling for a malformed address, but the schema's format constraint largely covers that.

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

Parameters4/5

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

Schema coverage is 100%, so the single email parameter is already documented. The description still adds real meaning by attaching a consent constraint ('given by its owner') and by explaining what the address is used for — receiving the confirmation link — which the schema only states tersely.

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 ('Subscribe an email address to The world according to capital, Tiago's newsletter') and scopes it to newsletter signup, which cleanly separates it from newsletter_stats and all the bookmark/collection siblings. An agent can identify the action 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 Guidelines5/5

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

Gives an explicit precondition ('Call it only with an address its owner asked you to sign up') and names an alternative path that requires no email at all (the RSS feed). Both the when and the when-not are stated, not inferred.

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