Skip to main content
Glama
ServiceBox MCP Server

ServiceBox MCP Server

servicebox_type

Type text into a specific numbered field on the current ServiceBox page using the field number from the last read.

Instructions

Type text into a numbered field on the current ServiceBox page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>",
      "text": "<text>"
    },
    "name": "servicebox_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the entire behavioral burden, and it does not say whether existing text in the field is replaced or appended, whether the field is focused first, whether typing submits the form, or what happens on an invalid field number. These are the questions an agent needs answered before invoking an input-mutating action on a live page.

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 no filler or repetition. It is efficient, though its brevity contributes to the missing behavioral detail rather than compensating for it.

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

Completeness2/5

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

For an unannotated page-interaction tool with no output schema, the definition leaves too much open: state prerequisites, replace-vs-append behavior, failure modes, and any confirmation of success are all absent. A short tool like this still needs those cues for reliable invocation.

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 description coverage is 100%, so both parameters are already documented, including 'Field number from the last read' for element. The description adds only the framing that the field is numbered and on the current page, which the schema largely covers. 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 states a specific verb and resource: 'Type text into a numbered field on the current ServiceBox page.' That is clearly distinct from siblings like servicebox_click or servicebox_read, which act on the page differently. It stops short of naming or contrasting an alternative explicitly, which keeps it out of 5 territory.

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 by 'on the current ServiceBox page', which signals that a page must already be open and the field already known. It never states the prerequisite that the field number comes from a prior servicebox_read, nor what to do if the index is stale. No alternatives or exclusions are given.

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