Skip to main content
Glama

Coline

Get an address for a place

alert_address_create
Idempotent

Makes (or returns) the place's one address. Paste the URL into any tool's webhook settings, or send mail to the email form. Use it when someone asks to send a tool's events somewhere ("send our deploys here", "post errors in this channel"), not a goal: hand them the URL and email to paste.

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": {
      "workspace": "<workspace>",
      "place": "<place>"
    },
    "name": "alert_address_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false; the description usefully explains why idempotency holds — there is exactly one address per place, and an existing one is returned rather than duplicated. Beyond that it adds no permission requirements, side effects on existing addresses, or failure modes for a tool that performs a write.

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 core semantics are front-loaded and short, but the closing clause — “not a goal: hand them the URL and email to paste” — is grammatically tangled and takes a second read to parse. The quoted example phrases are useful, yet the delivery instruction is buried in the same run-on sentence.

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?

With an output schema present, the description needn't explain return values, and it covers the two things an agent most needs: it is a get-or-create, and the result is meant to be handed to the user for pasting. Missing only prerequisites (membership/scope) and any hint about the nested place selector.

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?

The description conveys nothing about the two inputs (workspace slug, place type/id); that meaning comes entirely from the schema, which sits at 50% coverage. It does implicitly define what the tool returns (URL + email), but says nothing about valid place types or how the place id relates to channels, agents, teams, or people.

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 concrete outcome: it “makes (or returns) the place's one address,” and clarifies the address is a webhook URL plus an email form. This distinguishes it from a plain lookup, though it never names the sibling alert_address_get, so the get-vs-create boundary is only implied by the parenthetical.

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 gives a recognizable trigger with concrete user phrasings (“send our deploys here,” “post errors in this channel”) and an explicit exclusion (“not a goal”). It does not name the alternative tool (alert_address_get / alert_addresses_list), so routing to a sibling is left to inference.

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