Skip to main content
Glama

site_status

Read-only

The status of one Property in your LiftMCP organisation, or of all of them if no propertyId is given.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "site_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertyIdNoA Property id; leave out to list all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the scoping behavior (all Properties when the id is omitted), but says nothing about what the status result includes, how large an all-Properties response might be, or any auth/rate considerations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the resource and immediately followed by the scope condition. No filler, though the phrase 'in your LiftMCP organisation' is slightly padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one optional parameter and no output schema, the definition is structurally simple enough, but 'status' remains undefined and there is no output description to compensate, leaving an agent unsure what the call actually returns.

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 single parameter already documents 'leave out to list all'. The description restates that same branch without adding format, expected id shape, or error behavior beyond the schema.

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 names a specific resource (the status of a Property in the LiftMCP organisation) and states the two scopes: a single Property when propertyId is supplied, all of them otherwise. It never clarifies what 'status' actually contains, and it does not distinguish itself from siblings like check_site_readiness or verify_site, which sound closely related.

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 through the parameter branch: pass propertyId for one Property, omit it to list all. There is no explicit guidance on when to choose this over check_site_readiness or verify_site, nor any prerequisite or exclusion stated.

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