Skip to main content
Glama

Are We Working

Get the link to sign up for text or email alerts

get_alert_signup_link
Read-only

Returns the business's status page link, where the person can tap 'Get alerts' to sign up themselves. Use this for TEXT alerts: text opt-in must be completed by the person on the web form, not by an agent. Text alerts may not be enabled yet.

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

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish read-only and closed-world behavior. The description adds important context beyond that: it returns a link for the person to tap, text opt-in cannot be completed by an agent, and text alerts may not be enabled. It does not describe output structure, but no output schema exists and the key behavioral constraint is disclosed.

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?

The description is three short sentences with no wasted wording. It front-loads the return value and then immediately provides the usage constraint and caveat. Every sentence earns its place.

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 simple one-parameter read-only tool with no output schema and full schema description coverage, the definition is complete enough. It explains what is returned, who must complete the signup, and the possibility that text alerts are not enabled. Nothing essential for correct selection or invocation is missing.

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 the handle parameter is already fully documented in the schema. The description does not add any parameter-specific meaning beyond what the schema provides. A baseline 3 is appropriate when the schema carries the parameter semantics.

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?

The description states a specific verb and resource: it returns the business's status page signup link. It also distinguishes the tool's scope by saying it is for TEXT alerts and that the person must complete opt-in on the web form. An agent can tell this apart from request_email_alerts 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 Guidelines4/5

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

It clearly says when to use the tool: for TEXT alerts where the person must complete opt-in themselves. It also gives a caveat that text alerts may not be enabled yet. It stops short of explicitly naming request_email_alerts as the alternative for email alerts, so it is strong but not fully explicit about alternatives.

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