Skip to main content
Glama
Sign In
MYOB Codex MCP

MYOB Codex MCP

by jaeko44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

myob_invoice_prepare_create

Prepare a sales invoice in MYOB, enabling review and approval before final commit.

Instructions

Prepare creation of a sales invoice. Requires approval before commit.

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": {
      "json_body": "<json_body>"
    },
    "name": "myob_invoice_prepare_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
layoutNoService
json_bodyYes
business_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/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 discloses that the tool only prepares creation (not immediate creation) and that approval is required before commit. However, it does not describe what happens upon preparation, the output, or any side effects.

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 sentences, both meaningful: the first states purpose, the second states the key constraint. It is front-loaded and waste-free, though it could include more detail.

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 preparation tool with a required nested json_body and no parameter documentation, the description is incomplete. It leaves the agent without workflow steps (what to do after preparation, how to approve/commit) and without parameter expectations. The output schema may help but is not referenced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no information about the json_body, layout, or business_id parameters. The tool requires a json_body object with unspecified structure, so the agent receives no guidance on how to populate it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool prepares creation of a sales invoice, using a specific verb ('prepare') and resource ('sales invoice'). This distinguishes it from sibling tools like myob_invoice_prepare_update and myob_invoice_prepare_delete, as well as from other entity prepare tools.

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?

The description states 'Requires approval before commit,' providing clear context about the workflow and when to use the tool (as a preparation step before approval/commit). It does not explicitly name alternatives or exclusions, but the workflow context is clear.

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