Skip to main content
Glama
Sign In
myob-mcp

myob-mcp

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

myob_click

Clicks a numbered element on the current MYOB page so AI agents can perform approved invoice, bill, payment, and customer actions.

Instructions

Click a numbered element on the current MYOB page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "myob_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden and does not meet it. It doesn't say whether a click navigates, submits a form, mutates server state, waits for a page load, or what happens when the element number is stale or invalid — all critical for an action that can trigger writes.

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?

One short, front-loaded sentence with zero filler and the action leading. Its brevity borders on under-specification rather than being genuinely efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a browser-automation click with no annotations and no output schema, the definition omits the read-then-click sequencing, post-click behavior, and failure modes. An agent could call it correctly only by guessing at the surrounding workflow.

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 schema already explains 'Element number from the last read' with a minimum of 1. The description's 'numbered element' only echoes that, adding no format, range, or staleness details beyond 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?

Specific verb 'click' plus a specific resource, 'numbered element on the current MYOB page', which is more concrete than the sibling names (read, type, open, close, status, guide) would suggest. It doesn't explicitly contrast itself with myob_type or myob_read, but the action is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The sentence says what to do but never says when to choose this over myob_read or myob_type, nor does it state the prerequisite that the page must have been read first. Any when-to-use guidance must be inferred from the phrase 'on the current MYOB page'.

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