Skip to main content
Glama

xero_reports_aged_payables

Retrieve an Aged Payables report to view outstanding supplier bills grouped by payment due date age.

Instructions

Get an Aged Payables report showing outstanding supplier bills by age.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesReport date in YYYY-MM-DD format (required)

Implementation Reference

  • Schema definition for xero_reports_aged_payables tool. Defines its name, description, and input schema requiring a 'date' string in YYYY-MM-DD format.
    {
      name: "xero_reports_aged_payables",
      description:
        "Get an Aged Payables report showing outstanding supplier bills by age.",
      inputSchema: {
        type: "object",
        properties: {
          date: {
            type: "string",
            description: "Report date in YYYY-MM-DD format (required)",
          },
        },
        required: ["date"],
      },
    },
  • Handler logic for xero_reports_aged_payables. Extracts the 'date' argument, calls the Xero API at Reports/AgedPayablesByContact, and returns the result as formatted JSON.
    case "xero_reports_aged_payables": {
      const { date } = args as { date: string };
      const response = await client.get("Reports/AgedPayablesByContact", {
        date,
      });
      return {
        content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
      };
    }
  • src/index.ts:267-269 (registration)
    Tool routing: all xero_reports_* tool calls (including xero_reports_aged_payables) are routed to handleReportTool in the reports domain.
    if (name.startsWith("xero_reports_")) {
      return await handleReportTool(name, toolArgs);
    }
  • src/index.ts:83-84 (registration)
    The reportTools array (containing the xero_reports_aged_payables schema) is registered into the tool list via getAllDomainTools() and returned on ListTools requests.
    case "reports":
      return reportTools;
  • Uses getClient() from src/utils/client.ts which returns a XeroClient instance making authenticated GET requests to the Xero API base URL https://api.xero.com/api.xro/2.0/.
    const client = getClient();
    
    switch (name) {
      case "xero_reports_profit_and_loss": {
        const { fromDate, toDate } = args as {
          fromDate: string;
          toDate: string;
        };
        const response = await client.get("Reports/ProfitAndLoss", {
          fromDate,
          toDate,
        });
        return {
          content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
        };
      }
    
      case "xero_reports_balance_sheet": {
        const { date } = args as { date: string };
        const response = await client.get("Reports/BalanceSheet", { date });
        return {
          content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
        };
      }
    
      case "xero_reports_aged_receivables": {
        const { date } = args as { date: string };
        const response = await client.get("Reports/AgedReceivablesByContact", {
          date,
        });
        return {
          content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
        };
      }
    
      case "xero_reports_aged_payables": {
        const { date } = args as { date: string };
        const response = await client.get("Reports/AgedPayablesByContact", {
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states 'Get', implying a read operation, but does not mention side effects, authentication needs, rate limits, or return behavior. This is minimal transparency for a tool that fetches data.

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, concise sentence that is front-loaded with the key information (action and resource). No extraneous words earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple report tool with one parameter and no output schema, the description is adequate. It could optionally mention the date format or default behavior, but it is sufficient for an agent to understand the basic purpose.

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 coverage is 100% with a single parameter ('date') already described in the input schema. The description adds no additional parameter meaning beyond the schema, so baseline score of 3 is appropriate.

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 (Get) and the resource (Aged Payables report), with a brief explanation of content (outstanding supplier bills by age). It distinguishes from sibling reports like aged_receivables by specifying supplier bills.

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?

The description provides no explicit guidance on when to use this tool versus alternatives (e.g., xero_reports_aged_receivables). The only differentiation is implicit in the name and resource description, but no direct when-to-use or when-not-to-use advice is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wyre-technology/xero-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server