Skip to main content
Glama

miocommerce_open

Open a MioCommerce page in your signed-in Cloud Browser to manage customers, bookings, quotes, invoices, and service provider schedules.

Instructions

Open a MioCommerce page in your signed-in Cloud Browser (default https://signin.miocommerce.com) to work with customers, bookings, quotes, invoices and service provider schedules.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://signin.miocommerce.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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 two useful behavioral facts: the page opens in an already signed-in Cloud Browser session (so authentication is pre-established) and the default landing URL. It does not say whether the call waits for page load, what happens with an invalid or unreachable URL, or what the tool returns, which matters for a navigation primitive.

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 the action, the environment, the default target, and the supported workflows. No filler, no repetition, nothing that could be cut without losing information.

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 navigation tool with no output schema, the description covers the what and the default destination, but is thin on session/loading behavior and on how it sequences with its click/type/read/close siblings. Enough to invoke correctly, not enough to invoke optimally.

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?

There is a single optional url parameter with 100% schema description coverage, so the schema already documents both its meaning and its default, and the description merely restates the same default. Baseline 3 applies because the schema does the work and the description adds no format hints or constraints beyond it.

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 (open) and resource (a MioCommerce page in the signed-in Cloud Browser) and enumerates the domain objects it exposes (customers, bookings, quotes, invoices, schedules). An agent can tell this is a navigation/entry-point tool rather than an interaction tool, though the differentiation from siblings like miocommerce_click or miocommerce_read is left implicit.

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 phrase 'to work with customers, bookings, quotes, invoices and service provider schedules' implies this is the starting point for those workflows, but there is no explicit when-to-use rule, no mention of ordering relative to miocommerce_click/miocommerce_read/miocommerce_type, and no stated prerequisites such as needing an active browser session.

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