Skip to main content
Glama
ConstructionOnline MCP Server

ConstructionOnline MCP Server

constructiononline_status

Verify your Cotlet.dev account, available credits, and ConstructionOnline connection are ready before running construction management workflows.

Instructions

Check that your Cotlet.dev account and ConstructionOnline are ready: account, credits and ConstructionOnline connection.

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": "constructiononline_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It never states that the tool is read-only/non-mutating, what it returns for each of the three checks, whether failures raise errors or report status, or whether it consumes credits to check credits — leaving the agent to guess the behavior of a diagnostic call.

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?

A single front-loaded sentence with zero waste; the verb and the three checked items are packed into one clause and nothing is repeated from the name or title.

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 no annotations and no output schema, the description is the only place a caller could learn what a status result looks like — per-check pass/fail, error shape, or remediation hints — and it supplies none of that. It is complete about what is checked but silent about what comes back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is fully closed (additionalProperties: false) and consistent with a parameterless status probe.

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?

States a specific verb ('Check') and enumerates the exact resources inspected: Cotlet.dev account, credits, and ConstructionOnline connection. This clearly separates it from the sibling tools, which are browser interaction verbs (click, open, read, type), so an agent can identify it as the pre-flight readiness check without opening a schema.

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?

The word 'ready' implies this is a pre-flight check to run before other operations, but the description never says so explicitly, nor does it state when not to call it or what to do if a check fails. Usage is inferable but not spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.