Skip to main content
Glama

Are We Working

Request email alerts for a business

request_email_alerts

Signs a person up to receive an email whenever a business's status changes. IMPORTANT: only call this after the person has explicitly agreed to the consent text below, and give them the chance to read it first. Never call it on a person's behalf without that agreement. The request is not active immediately: a business administrator must approve it before any email is sent. Email only; for text alerts use get_alert_signup_link.

Consent text to show the person: "I agree to receive email alerts from Are We Working when this business's operating status changes. Message frequency varies. I can unsubscribe at any time using the link in any alert."

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": {
      "handle": "<handle>",
      "name": "<name>",
      "email": "<email>",
      "consent": "<consent>"
    },
    "name": "request_email_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe person's name.
emailYesThe person's email address, exactly as they gave it.
handleYesThe business's handle: the last part of its status page URL (areweworking.org/{handle}), e.g. 'riverside-fab'. Use search_businesses if you only know the name.
consentYesMust be true, and only after the person has explicitly agreed to the consent text in this tool's description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds far more, notably that the request is inert until a business administrator approves it and that no email is sent before then. It also discloses the consent flow, message-frequency variability, and unsubscribe behavior.

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?

Purpose is front-loaded, followed by the critical consent gate, then the approval caveat and the email-vs-text routing rule — a sensible priority order. The quoted consent text is long but functional, since the person must be shown it verbatim; the only cost is overall length.

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

Completeness5/5

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

For a four-parameter write tool with no output schema, the description covers everything an agent needs: the consent prerequisite and text, the deferred-activation/approval model, and the email-only scope. Nothing material is missing for correct invocation.

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 parameter mechanics are already documented. The description still adds meaning: it supplies the actual consent text and the sequencing requirement ('give them the chance to read it first'), which flesh out why consent must be true rather than just that it must be. It does not add format or validation detail beyond the schema, so it falls short of a 5.

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: signs a person up for email alerts on a business's status changes. It also explicitly scopes itself to email and names the sibling for text alerts, so an agent can tell it apart from get_alert_signup_link without opening any 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 only after the person has agreed to the consent text and had a chance to read it), an explicit prohibition (never on a person's behalf without agreement), and an explicit alternative routing rule for text alerts. These are when/when-not/alternative statements, not implied guidance.

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