Skip to main content
Glama

miocommerce_read

Reads the current MioCommerce page text and numbered buttons, links, and fields, optionally limiting the read to a specific element for targeted page inspection.

Instructions

Read the current MioCommerce 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": "miocommerce_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/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 usefully disclose the shape of the observation (text plus numbered interactive elements), implying a read-only snapshot, but it does not state that it is non-mutating, whether it reflects live state, or how it behaves when nothing is open.

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?

One sentence with zero waste, front-loading the verb and resource before listing return contents. Nothing to trim.

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 one-optional-parameter read tool with no output schema, describing the returned contents is the key missing piece and it is supplied. Only edge-case behavior (no page open, stale vs live DOM) is absent.

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% and the single 'element' parameter is fully documented in the schema ('Read only inside this element'), so the baseline of 3 applies. The description text contributes nothing about scoping to a region, leaving that entirely to the schema.

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 gives a specific verb and resource — 'Read the current MioCommerce page' — and enumerates what comes back (text, numbered buttons, links, fields), which is what distinguishes it from the action siblings (click, type, open). It does not name an alternative, so a reader must infer that this is the passive inspection counterpart to those tools.

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?

'Current' page implies the tool only applies after the page is open, but there is no explicit when-to-use or when-not guidance, no advice on re-reading after a click or navigation, and no mention of what happens if no page is loaded. Usage is only implied by context.

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