Skip to main content
Glama
ServiceBox MCP Server

ServiceBox MCP Server

servicebox_open

Opens a ServiceBox page in your signed-in Cloud Browser session so you can work with dispatch work orders, compare job costs, and manage quotes and invoices.

Instructions

Open a ServiceBox page in your signed-in Cloud Browser (default https://jb.jobboxsoft.com) to work with dispatch work orders, compare job costs and manage quotes 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": "servicebox_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://jb.jobboxsoft.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 behavioral burden. It usefully discloses that the browser is already signed in (so no auth step is expected) and gives the default URL, but says nothing about whether navigation is idempotent, what happens on an invalid or unreachable URL, or whether the call returns a page handle versus content.

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-loaded with the action and the default URL, with the trailing capability list giving useful context about what the page is for. The feature enumeration ("dispatch work orders, compare job costs and manage quotes and invoices") is slightly promotional but still earns its place as framing.

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, non-destructive navigation tool with no output schema, the description covers the essentials: what opens, where, and under what session. It falls short on what the agent gets back and what sibling call (read, status, click) should follow, which matters in a multi-tool browser automation suite.

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?

The single url parameter is fully documented in the schema, including its default value, so the schema already does the work and 3 is the baseline. The description only restates the default and adds the framing that the URL is a ServiceBox page rendered in a signed-in browser session, which is marginal 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 and resource: "Open a ServiceBox page in your signed-in Cloud Browser," and names the default target URL. The verb "open" is naturally distinct from sibling verbs like click, close, read, and type, though the description never explicitly contrasts itself with them.

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: an agent infers you open a page before reading or clicking it, and the mention of work orders, job costs, and invoices hints at what the page is for. There is no explicit statement of when to use this versus servicebox_read or servicebox_status, and no prerequisites or exclusions.

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