Skip to main content
Glama
Sign In
MYOB Codex MCP

MYOB Codex MCP

by jaeko44
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

myob_entity_list

List records for any supported MYOB entity using the endpoint registry, with filtering, ordering, and pagination options for efficient data retrieval.

Instructions

List records for a supported MYOB entity using the endpoint registry.

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": {
      "entity": "<entity>"
    },
    "name": "myob_entity_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
entityYes
filterNo
orderbyNo
max_itemsNo
business_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for disclosing behavior. It only mentions 'using the endpoint registry', but does not explain how unsupported entities are handled, pagination behavior, response format, or authentication needs. This is a significant transparency gap for an unannotated tool.

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?

The description is a single, front-loaded sentence that efficiently states the core action. However, it may be too terse, sacrificing necessary detail for brevity.

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?

Given the generic nature and six parameters with zero schema descriptions, this description is far from complete. It does not cover how to specify entities, apply filters, or interpret the output, making it insufficient for an agent to use the tool correctly.

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 does not compensate. It only vaguely references the entity parameter, leaving top, filter, orderby, max_items, and business_id completely unexplained. The agent has no idea how to use these parameters effectively.

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?

The description states the tool lists records for a supported MYOB entity, using 'List' as a specific verb and referencing the entity resource. It implicitly distinguishes itself from specialized list tools (e.g., myob_account_list) by being entity-generic, though it doesn't explicitly say so.

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?

No guidance is provided on when to use this generic tool versus the many specialized list tools (e.g., myob_account_list, myob_customer_list). There is no mention of alternatives, prerequisites, or exclusions.

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