Skip to main content
Glama
ConstructionOnline MCP Server

ConstructionOnline MCP Server

constructiononline_open

Opens a ConstructionOnline page in your signed-in Cloud Browser so you can work with projects, estimates, RFIs, and invoices.

Instructions

Open a ConstructionOnline page in your signed-in Cloud Browser (default https://app.constructiononline.com) to work with construction projects, estimates, RFIs and invoices.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://app.constructiononline.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description has to carry the behavioral load. It usefully discloses that the browser is already signed in and that the default target is the app root, but it does not say whether opening replaces the current page, whether session/auth failures are possible, or whether page content is returned or must be fetched via constructiononline_read.

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 front-loaded sentence with the action and context first, then domain examples. The trailing list of construction artifacts is mildly decorative but quickly communicates scope.

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?

For a simple one-parameter navigation tool this is close to adequate, but with no output schema the description should clarify what the agent gets back after opening (a live page vs. content) and how it relates to constructiononline_read. That omission leaves the follow-up step ambiguous.

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% for the single optional url parameter, so the schema already defines it fully. The description merely restates the default URL, adding no syntax, format, or navigation semantics 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?

States a specific verb ('Open') and resource ('a ConstructionOnline page') and situates it in 'your signed-in Cloud Browser', which separates it from siblings like constructiononline_read or constructiononline_click. It stops short of naming any sibling or explicitly contrasting behaviors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The purpose clause hints at domain use, but there is no explicit when-to-use, when-not, prerequisite, or alternative ('open this before calling read/click'). The agent must infer that this tool navigates the Cloud Browser session first.

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