Skip to main content
Glama
ConstructionOnline MCP Server

ConstructionOnline MCP Server

constructiononline_guide

Explains how to work in ConstructionOnline, including its screens and sign-in link. Call this first to learn project, estimate, RFI and invoice workflows.

Instructions

How to work in ConstructionOnline (construction projects, estimates, RFIs and invoices): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in ConstructionOnline, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It implies a passive informational lookup (screens and a sign-in link) and does not suggest mutation, but it never states what form the answer takes, whether the sign-in link is safe to surface, or any auth/session requirement. Adequate but thin for a tool with zero annotation coverage.

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?

Two short sentences with no filler. The main weakness is placement: the decisive instruction 'Call this first' is buried at the end rather than front-loaded, so an agent skimming may miss the sequencing rule.

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?

The tool is simple (one optional param, no output schema, no nested objects), so little is required, but the description leaves under-specified what the agent receives back — prose instructions, a URL, screen names — and whether the result depends on the 'task' value. Enough to call it, not enough to predict its output.

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?

There is a single optional parameter and schema description coverage is 100%, with the schema itself defining 'task' as 'What you want done in ConstructionOnline, in your words.' That meets the baseline for a one-parameter tool; the description adds only marginal framing that the task should concern ConstructionOnline work.

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 — guidance on ConstructionOnline screens and the sign-in link — and its parenthetical lists the domain areas covered (projects, estimates, RFIs, invoices). It is reasonably distinct from the browser-action siblings (click/open/type/read), though 'How to work in ConstructionOnline' is a phrase rather than a crisp statement of what the tool actually returns.

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?

'Call this first' gives explicit ordering guidance that no sibling tool provides, which is the key usage decision for an onboarding/guide tool. It does not, however, state when not to call it or how it relates to the click/open/read tools once the agent has the guidance.

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