Skip to main content
Glama
ServiceBox MCP Server

ServiceBox MCP Server

servicebox_guide

Guides users through ServiceBox screens to dispatch work orders, compare job costs, manage quotes and invoices, and locate the sign-in link.

Instructions

How to work in ServiceBox (dispatch work orders, compare job costs and manage quotes and invoices): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in ServiceBox, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/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 disclose the payload shape at a high level (screens plus a sign-in link), which is helpful, but it never states that the tool is read-only, that it makes no changes, or whether the task argument changes what comes back.

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 compact sentence with the covered domains in a parenthetical and the call-order instruction last. The parenthetical is slightly dense but every clause carries information; nothing is wasted.

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 single-parameter guide tool with no output schema, the description covers what it is and when to call it. The remaining gap is the relationship between the `task` input and the returned content, which an agent would need in order to phrase the argument usefully.

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 coverage is 100% for the single optional `task` parameter, so the baseline of 3 applies. The description adds nothing about how `task` is used, whether it narrows the returned guidance, or whether omitting it returns a general overview.

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 names the resource (ServiceBox) and the kind of content returned: an orientation guide covering screens and the sign-in link, scoped to dispatch, job costs, quotes and invoices. That is enough to distinguish it from the action-oriented siblings (click, open, read, type), though it never names them explicitly.

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

Usage Guidelines4/5

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

"Call this first" gives an explicit ordering rule that tells the agent this is the entry point before invoking the other servicebox_* tools. There is no when-not guidance or note on whether it is still useful once a session is underway.

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