Skip to main content
Glama
Sign In
myob-mcp

myob-mcp

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

myob_read

Reads the current MYOB page to return its text plus numbered buttons, links, and fields, optionally scoped to one element. Use it to inspect page content and identify controls before acting.

Instructions

Read the current MYOB 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": "myob_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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?

No annotations are supplied, so the description carries the full burden. It usefully discloses the shape of what comes back (text plus numbered buttons, links, fields), which substitutes for the missing output schema, but it says nothing about whether the page must be loaded first, whether reading has side effects, or how the numbering is generated.

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, front-loaded with the verb and target, then the payload. No filler, no restatement of the tool name, and every clause adds 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 read tool with no annotations and no output schema, the description does cover the return content, but it leaves the crucial mechanics unexplained: how the numbered items relate to the 'element' parameter and to myob_click. An agent must guess at the numbering contract to chain calls.

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 optional 'element' parameter is documented as 'Read only inside this element.' The description never mentions scoping-to-an-element, though the mention of 'numbered buttons, links and fields' hints at the numbering vocabulary the parameter relies on. Baseline 3 is appropriate.

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 ('Read') and a specific resource ('the current MYOB page'), then enumerates the returned content (text, numbered buttons, links, fields). It is clearly distinguishable from mutating siblings like myob_click or myob_type, though it never names a sibling or an alternative.

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 the word 'current' — the agent must infer this is the inspection step after myob_open and before myob_click/myob_type. There is no explicit when-to-use, when-not-to-use, or named alternative such as myob_status.

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

Deploy Server

Other Tools