Skip to main content
Glama

extrabat_open

Opens a page in your signed-in Extrabat Cloud Browser (default https://myextrabat.com) to manage customers, quotes, site visits, and after-sales workflows.

Instructions

Open a Extrabat page in your signed-in Cloud Browser (default https://myextrabat.com) to work with customers, quotes, site visits and after-sales.

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": "extrabat_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://myextrabat.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 burden; it does contribute the useful detail that the browser is "signed-in," implying an authenticated session is reused rather than credentials supplied. It does not say what happens on failure, whether an already-open session is reused or replaced, or whether any page content is returned, leaving notable behavioral gaps for a navigation tool.

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 action, environment and default up front and no wasted clauses. Minor grammar awkwardness ("a Extrabat") and a purpose clause that could be tighter keep it just short of ideal.

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-optional-parameter navigation tool with no output schema, the definition covers what it does and the default target, which is close to sufficient. It stops short of telling the agent what state results after opening (e.g., that extrabat_read should follow), which matters for chaining in this sibling family.

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?

Only one optional parameter and schema description coverage is 100%, so the schema already documents the url field and its default. The description repeats the default URL rather than adding new semantics such as accepted path formats or constraints, so the baseline of 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?

States a specific verb and resource: "Open a Extrabat page in your signed-in Cloud Browser," which clearly separates it from siblings like extrabat_close, extrabat_read, or extrabat_click. It also scopes the purpose (customers, quotes, site visits, after-sales), though it never names a sibling to contrast with explicitly.

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 verb "open" and the business-domain phrasing imply when to use it (starting a browser session on Extrabat), but there is no explicit when-to-use/when-not guidance and no pointer to extrabat_read or extrabat_guide for follow-up actions. Usage is inferable rather than stated.

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