Skip to main content
Glama

workquote_open

Opens a WorkQuote page in your signed-in Cloud Browser so you can manage estimates, jobs, and invoices.

Instructions

Open a WorkQuote page in your signed-in Cloud Browser (default https://web.workquote.app) to work with manage estimates, jobs 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": "workquote_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://web.workquote.app

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 navigation happens in a signed-in Cloud Browser session at a default URL, which implies an auth prerequisite. However, it omits key behavioral facts: whether a call replaces an already-open page or opens a new one, whether it is idempotent, and what happens on failure.

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?

A single front-loaded sentence with the verb and target stated first, which is well structured. Minor waste: the default URL duplicates the schema, and the phrase 'to work with manage estimates' is garbled and costs a small amount of clarity.

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-optional-param navigation tool with no output schema, the definition covers the essentials of target and environment. It is still incomplete on session-state semantics (replace vs. new tab, effect on prior page), which is the main thing an agent would need before sequencing this with the click/type/close siblings.

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 one optional parameter with 100% schema description coverage; the schema already says 'Page to open. Default: https://web.workquote.app'. The description repeats that same default URL without adding format expectations, validation rules, or examples, so baseline 3 applies.

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 uses a specific verb and resource: 'Open a WorkQuote page in your signed-in Cloud Browser'. This clearly separates it from siblings like workquote_close or workquote_read, which act on the page rather than establishing it. The trailing clause 'to work with manage estimates, jobs and invoices' is grammatically mangled but still signals the domain purpose.

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 mention of a 'signed-in Cloud Browser' hints that this is a prerequisite/setup step before click/type/read actions. The description never states when to call this versus workquote_status or workquote_guide, nor what to do if a page is already open. An agent must infer the ordering from the sibling names.

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