Skip to main content
Glama

Coline

Get a place's address

alert_address_get
Read-onlyIdempotent

Gets the address a channel, crew member, team or your Inbox receives events at: a URL any tool can POST to and an email address. Null when the place has none 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": {
      "workspace": "<workspace>",
      "place": "<place>"
    },
    "name": "alert_address_get"
  }
}

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.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's value is in disclosing the return semantics: a URL that any tool can POST to plus an email address, and explicitly returning null when no address is configured. It does not cover authorization requirements (e.g. whether you can read another person's Inbox address), which keeps it short of a 5.

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?

Two compact sentences, both front-loaded: the first states the action and the return contents, the second handles the null case. Nothing is repeated and no sentence is filler.

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 detail return values, and with annotations carrying the safety profile the description only needs to add the null-case nuance, which it does. The main residual gap is not saying where the address comes from or how to set one if absent, but overall it is sufficient for a two-parameter read tool.

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 50% and the nested place.type/id fields already carry descriptions and an implied enum, so the schema does much of the work. The description restates the place taxonomy (channel, crew member, team, Inbox) but adds no format, slug, or lookup guidance beyond what the schema provides. Baseline 3 applies.

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 uses a specific verb+resource ("Gets the address") and immediately enumerates the place types (channel, crew member, team, Inbox) plus the return shape (a POST-able URL and an email address). It does not explicitly differentiate itself from the closely related sibling alert_addresses_list, but the scoping to a single place is clear.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers you call this to read one place's ingest address. There is no explicit when-to-use, no guidance on choosing alert_addresses_list for enumerating addresses, and no pointer to alert_address_create when the result is null, even though the description volunteers that null case.

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