Skip to main content
Glama

Are We Working

Get a business's current status

get_business_status
Read-only

Returns the live operating status of a business on Are We Working: Open, Partially open, Closed, or an emergency status (Tornado Warning: Take Shelter Immediately, or Emergency Evacuation), with the business's note (for example a weather closure or delayed start) and when it was last updated. Use this to answer 'is X open / working today?'.

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_business_status"
  }
}

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?

Annotations already establish that this is a read-only, non-open-world operation. The description adds useful behavioral detail by listing the returned statuses, the business note, and the last-updated timestamp, which compensates for the lack of an output schema.

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 front-loaded with the core return value and status categories. It is compact, and every sentence contributes either to describing the output or to explaining the tool's intended use.

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, the description covers the important return information: possible statuses, note content, and last-updated time. Combined with the fully documented handle parameter and read-only annotation, an agent has enough context to call it correctly.

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 schema fully documents the single handle parameter, including its URL-derived format and the fallback to search_businesses. The description does not add any parameter meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 live operating status of a business. It enumerates the possible status values and distinguishes the live status from historical information by emphasizing 'live' and 'last updated'.

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 clear usage context: answering whether a business is open or working today. It does not explicitly name alternatives such as get_status_history or state when not to use this tool, so it falls short of full when/when-not 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