Skip to main content
Glama
Sign In
myob-mcp

myob-mcp

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

myob_guide

Get guidance on MYOB screens, invoices, bills, payments, and the sign-in link; call first before starting any MYOB task.

Instructions

How to work in MYOB (invoices, bills and payments): 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": "myob_guide"
  }
}

Input Schema

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

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?

No annotations exist, so the description carries the full disclosure burden. Calling it 'How to work in MYOB' plus a 'sign-in link' implies a read-only reference/lookup with no side effects, but it never states what comes back (text, screenshots, URLs), whether the sign-in link is authenticated, or that nothing is mutated. Those gaps are material for an agent deciding whether it is safe to call.

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?

Two short clauses with no wasted words, and the scope parenthetical is efficient. The strongest routing signal ('Call this first') sits at the very end rather than the front, which slightly weakens the front-loading.

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 simple one-parameter guide tool this is close to complete, and the sequential hint covers the main decision an agent must make. However, with no output schema and no annotations, the definition never says what form the guide arrives in or what the sign-in link resolves to, leaving the agent guessing about the return payload.

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 (task) with 100% schema description coverage, so the schema already documents it fully. The description adds no guidance on how to phrase the task or whether it can be omitted, so the baseline 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?

Names the resource (MYOB) and the content it covers (screens, sign-in link) for the invoices/bills/payments area, and the verb 'how to work in' at least frames it as an orientation/guide tool. It is distinguishable from the action-oriented siblings (myob_click, myob_open, myob_type) by being the explanatory entry point, though the verb itself is softer than an ideal concrete verb like 'Get MYOB screens and sign-in link'.

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?

'Call this first' gives explicit, actionable sequencing guidance that selects this tool over all siblings. It stops short of describing when-not to use it or what to do if the agent already knows the screens, but the ordering instruction is unambiguous.

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