myob-mcp

myob_type

Type text into a numbered field on the current MYOB page to automate data entry for invoices, bills, or customer records.

Instructions

Type text into a numbered field 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>",
      "text": "<text>"
    },
    "name": "myob_type"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	Text to type.
`element`	Yes	Field number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 14, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are supplied, so the description bears the full disclosure burden. It never states whether typing replaces or appends to existing text, whether it clears the field first, whether keystrokes fire page events that might submit the form, or what happens on failure. For an unannotated mutating UI action this is a substantial omission.

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?

A single front-loaded sentence with no filler. It is appropriately terse, though the brevity comes partly at the cost of the behavioral detail noted elsewhere.

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?

With no annotations and no output schema, the description must convey outcome semantics, and it does not: an agent cannot tell whether success means the text is committed, whether a subsequent click is required, or how errors surface. The stated purpose is clear but the surrounding contract is thin for a state-mutating UI tool.

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 description coverage is 100%, so both parameters are already documented ('Text to type.' and 'Field number from the last read.'). The description reinforces that the field is numbered and page-scoped but adds no format, length, or escaping semantics beyond the schema – 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?

States a specific verb (type) and target (a numbered field on the current MYOB page), which cleanly separates it from myob_click and myob_read. The only shortfall is that it doesn't explicitly say what it is not, but the verb+resource 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 Guidelines3/5

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

Usage is implied through the phrase 'current MYOB page' and the schema's 'field number from the last read', which hint at a read-then-type workflow. There is no explicit when-to-use or when-not-to-use guidance, and no mention of prerequisites such as the field needing focus.

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

Deploy Server