Skip to main content
Glama

Are We Working

Get a business's recent status changes

get_status_history
Read-only

Returns the most recent status changes for a business, newest first, each with the status, note, and time. Useful for 'when did it close?' or 'how often does this change?'.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many changes to return.
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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing result ordering (newest first) and the per-record payload (status, note, time), which matters since no output schema exists. It does not mention what happens for an unknown handle or whether history is truncated.

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 sentences with no filler; the return content and ordering are front-loaded before the use-case examples. Nothing could be removed without losing information.

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?

For a two-parameter read with no output schema, the description covers the essentials: what is returned, in what order, and what questions it answers. The only gap is edge behavior for an unknown handle or an empty history.

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%, with both the handle format and the limit bounds/default fully documented in the schema. The description adds nothing about parameters beyond what the schema already states, so the 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?

Specific verb and resource: 'Returns the most recent status changes for a business', plus the ordering ('newest first') and the returned fields ('status, note, and time'). This implicitly separates it from a current-status lookup like get_business_status, but no sibling is named or contrasted explicitly.

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?

Gives concrete use cases ('when did it close?', 'how often does this change?') that map cleanly onto a history query, which is clear usage context. It stops short of naming when NOT to use it or pointing to an alternative for current-state questions.

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