Skip to main content
Glama

miocommerce_guide

Provides guidance on navigating MioCommerce screens and sign-in for managing customers, bookings, quotes, invoices, and service provider schedules; call this first to orient a task.

Instructions

How to work in MioCommerce (customers, bookings, quotes, invoices and service provider schedules): 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": "miocommerce_guide"
  }
}

Input Schema

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

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?

No annotations are provided, so the description must carry the behavioral burden. It implies this is an informational guide by describing screens and the sign-in link, but it does not explicitly state that it is read-only, what form the guidance takes, or how the optional task parameter affects the response.

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?

The definition is two short sentences with no wasted wording. It front-loads the tool's scope and follows with the critical ordering instruction, making it easy to scan.

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 low-complexity guide tool with one optional parameter and no output schema, the description adequately states what it covers and when to call it. A slightly fuller statement of what the response contains would close the remaining gap.

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?

The single optional task parameter is fully documented in the schema as 'What you want done in MioCommerce, in your words.' The description adds no further meaning about how the task string is interpreted or whether it customizes the guide.

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 identifies MioCommerce as the resource and names the covered domains (customers, bookings, quotes, invoices, service provider schedules) plus screens and the sign-in link. It is clear what the tool is for, though the phrasing is more descriptive than a crisp verb+resource statement.

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?

The instruction 'Call this first' gives explicit ordering guidance for when to use this tool relative to the action-oriented siblings. It does not name alternatives or state when not to use it, so it stops short of full when/when-not guidance.

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