Skip to main content
Glama
ServiceBox MCP Server

ServiceBox MCP Server

servicebox_read

Read the current ServiceBox page to extract visible text and numbered buttons, links, and fields, optionally limited to one element, so an agent can inspect page content before acting.

Instructions

Read the current ServiceBox page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden. It clearly implies a non-mutating read and identifies what page elements are returned, but it omits details such as whether it reads only visible content, how numbered elements relate to actions, authentication needs, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It immediately gives the action, target, and returned content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with one optional parameter and no output schema, the description adequately explains what is read and what kinds of page elements are returned. Minor gaps remain around behavioral details and how the element parameter relates to the listed numbered elements, but the schema covers the parameter itself.

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%, so the sole optional 'element' parameter is already documented as 'Read only inside this element.' The description adds no further explanation of how element numbers map to buttons, links, or fields, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Read) and resource (the current ServiceBox page), then enumerates the returned page contents: text, numbered buttons, links, and fields. This clearly separates it from action-oriented siblings like servicebox_click and servicebox_type.

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?

The usage is implied: read the current page when you need its visible content or interactive elements. However, it does not explicitly say when to use this instead of servicebox_guide, servicebox_status, or servicebox_open, nor does it state prerequisites or exclusions.

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