Skip to main content
Glama

provision_open

Opens a Provision page in your signed-in Cloud Browser to work with pre-construction bid documents, scope gaps, scope packages, contract risks, and review checklists.

Instructions

Open a Provision page in your signed-in Cloud Browser (default https://provision.com) to work with pre-construction bid documents, scope gaps, scope packages, contract risks and review checklists.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://provision.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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 usefully discloses that the page opens in the user's already signed-in Cloud Browser session, which tells the agent auth is inherited rather than prompted. However, it does not say what the call returns (page handle, URL, confirmation), whether existing tabs are replaced, or whether it waits for page load.

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-loading the action and target, with the default URL placed inline where it is relevant. The trailing list of document types is somewhat long but does convey what the opened page is for, so it earns most of its space.

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 one-optional-parameter launch tool with no output schema, the description covers what happens and where, but leaves open what the agent receives back and whether a browser session must already exist. Those are the main gaps an agent would hit when calling it.

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?

With a single optional parameter at 100% schema description coverage, the schema already documents the url field and its default. The description restates the same default (https://provision.com) without adding format guidance, allowed hosts, or behavior for invalid URLs, so it adds little beyond the structured field.

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 Provision page in your signed-in Cloud Browser') and names the domain of work the page supports. It is clearly a navigation/launch action distinguishable from action siblings like provision_click or provision_type, though it does not explicitly contrast itself with provision_status or provision_guide.

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: the agent can infer this is the entry point for starting work on bid documents, scope gaps, packages, risks, and checklists. There is no explicit when-to-use, when-not-to-use, or named alternative such as provision_guide for guidance or provision_status for state checks.

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