Skip to main content
Glama
RPasquale

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

myob_create_bill

DestructiveIdempotent

Create a bill in MYOB by routing through authorized connector accounts, using idempotency keys and approval references to ensure reliable, governed write operations.

Instructions

Myob connector operation create_bill (platform tool myob.create_bill).

Routes only through the exact project/account governed connector authority.

Args: arguments: JSON string of arguments for the connector operation. project_id: Authenticated Project UUID. project_ref: Exact project correlation reference. connector_account_ref: Project-bound connector account alias. idempotency_key: Stable business-action identity. effect: Claimed read or write effect; Spring verifies it. approval_ref: Approved platform task UUID when resuming a write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
effectNo
argumentsNo{}
project_idNo
project_refNo
approval_refNo
idempotency_keyNo
connector_account_refNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / approval_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Approval Ref"
+}
    • addedInput schema / properties / connector_account_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Connector Account Ref"
+}
    • addedInput schema / properties / effect
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Effect"
+}
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Idempotency Key"
+}
    • addedInput schema / properties / project_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Id"
+}
    • addedInput schema / properties / project_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Ref"
+}
  2. First observedv0.1.0

TDQS

C2.7/5.0
Behavior4/5

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

Annotations already establish readOnly=false and destructiveHint=true, so the description doesn't need to repeat that. It adds useful behavioral context: the routing authority constraint, the effect parameter being verified by Spring, idempotency_key as a stable business identity, and approval_ref being required when resuming a write. These details go beyond the annotations and clarify the governance/approval requirements for write operations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and the Args list is well-structured. However, the opening line 'Myob connector operation `create_bill` (platform tool `myob.create_bill`)' is redundant with the tool name, and the routing sentence is somewhat vague. Overall it is not bloated, but the first line wastes space restating the obvious.

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 7 optional parameters and zero schema descriptions, the description needs to fully support correct invocation, but it leaves the core payload ('arguments') undefined. It also provides no guidance on what constitutes a valid MYOB bill or how this tool relates to the many sibling bill-creation tools. Although an output schema exists, the missing semantic payload documentation is a serious gap for a destructive write operation.

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?

Because schema description coverage is 0%, the description is the only source of parameter meaning. It provides one-line explanations for all seven parameters, which is valuable. However, the central parameter 'arguments' is only described as 'JSON string of arguments for the connector operation' — a circular explanation that doesn't specify what fields the MYOB bill payload should contain, leaving the agent unable to construct the actual request body.

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

Purpose2/5

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

The description opens with 'Myob connector operation `create_bill`', which is essentially a restatement of the tool name and provides no actual explanation of what creating a bill entails. It does not describe the business action (e.g., recording a bill in MYOB) nor differentiate from sibling bill-creation tools like xero_create_bill or quickbooks_create_bill. The only non-tautological sentence is a routing constraint, not a purpose statement.

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?

There is no guidance on when to use this tool versus alternatives. The description mentions that it 'Routes only through the exact project/account governed connector authority', but that is a routing constraint rather than a selection criterion. The sibling list includes multiple create_bill tools across different accounting platforms, and nothing here helps an agent decide to pick myob_create_bill over them.

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