Skip to main content
Glama
Sign In
MYOB Codex MCP

MYOB Codex MCP

by jaeko44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

myob_business_remove_authorization

Remove locally stored OAuth tokens for a MYOB business by providing its business ID, revoking access and clearing authorization data.

Instructions

Remove locally stored OAuth tokens for one MYOB business/company file.

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": {
      "business_id": "<business_id>"
    },
    "name": "myob_business_remove_authorization"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

The description discloses that tokens are 'locally stored,' which is informative, but it does not state whether remote authorization is also revoked, whether removal is reversible, or how it affects default business selection. With no annotations, the description carries the full transparency burden but only partially fulfills it.

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

Conciseness5/5

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

The description is a single sentence that is direct, action-focused, and free of unnecessary words. It front-loads the verb and resource with maximum efficiency.

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 single-parameter tool, the description is adequate but lacks important context about side effects (e.g., whether server-side authorization is invalidated) and post-removal behavior. There is no output schema, so return values are not explained; however, simplicity is a mitigating factor.

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?

The one parameter (business_id) is not described in the schema, and the description's phrase 'one MYOB business/company file' indirectly clarifies its purpose. However, it does not explicitly explain what business_id represents, its format, or how to obtain it, so it adds limited value beyond the type definition.

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 action ('Remove locally stored OAuth tokens') and the scope ('one MYOB business/company file'), distinguishing it from global logout tools like myob_oauth_logout. It is specific, verb-first, and resource-targeted.

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 explicit guidance on when to use this tool versus alternatives such as myob_oauth_logout or myob_business_list_authorized. The description does not mention prerequisites, intended scenarios, or exclusion cases, leaving the agent to infer usage solely from the tool name.

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