Skip to main content
Glama

contractor_foreman_open

Open a Contractor Foreman page in your signed-in Cloud Browser to manage projects, estimates, and invoices.

Instructions

Open a Contractor Foreman page in your signed-in Cloud Browser (default https://contractorforeman.com) to work with manage projects, estimates 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": "contractor_foreman_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://contractorforeman.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?

With no annotations, the description carries the full burden. It does add a genuinely useful behavioral detail — that the page opens inside an already signed-in Cloud Browser session, so no auth step is needed — but it says nothing about whether navigation discards the current page state, what happens on an invalid or unreachable URL, or whether any content is returned.

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 verb and resource first and the default URL in parentheses. Minor waste in the awkward clause "to work with manage projects, estimates and invoices," which reads ungrammatically and could be tightened.

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-parameter navigation tool with no output schema this is close to sufficient, but an agent still cannot tell whether opening a page yields content or whether a follow-up read call is required, which matters for chaining with the sibling tools.

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?

There is a single optional parameter at 100% schema description coverage, so the baseline is 3. The description only restates the default URL that the schema already documents and adds no format, validation, or path-vs-absolute-URL guidance.

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 pairs a concrete verb ("Open") with a specific resource ("a Contractor Foreman page in your signed-in Cloud Browser") and names the default URL, so the action is unambiguous. It is reasonably distinct from siblings like read/click/type/close, but it never explicitly contrasts itself with them, so it stops short of a 5.

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 phrase "to work with manage projects, estimates and invoices" hints at the workflow context, and the sibling set suggests this is the entry point before click/type/read. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative for cases where the page is already open.

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