Skip to main content
Glama

xero_navigate

Browse available Xero tools organized by domain. Select a domain to see tool names and descriptions for managing contacts, invoices, payments, accounts, or reports.

Instructions

Discover available Xero tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain to explore: - contacts: Contact management - list, get, create, and search contacts (customers and suppliers) - invoices: Invoice management - list, get, create invoices and update their status - payments: Payment management - list, get, and create payments against invoices - accounts: Chart of accounts - list and view account details by type and class - reports: Financial reports - profit & loss, balance sheet, aged receivables, and aged payables

Implementation Reference

  • Tool definition and input schema for the xero_navigate tool, including the domain enum and description.
    const navigateTool: Tool = {
      name: "xero_navigate",
      description:
        "Discover available Xero tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.",
      inputSchema: {
        type: "object",
        properties: {
          domain: {
            type: "string",
            enum: [
              "contacts",
              "invoices",
              "payments",
              "accounts",
              "reports",
            ],
            description: `The domain to explore:
    - contacts: ${domainDescriptions.contacts}
    - invoices: ${domainDescriptions.invoices}
    - payments: ${domainDescriptions.payments}
    - accounts: ${domainDescriptions.accounts}
    - reports: ${domainDescriptions.reports}`,
          },
        },
        required: ["domain"],
      },
    };
  • Handler for xero_navigate tool calls. Extracts the domain argument, looks up the tools for that domain via getDomainTools(), and returns a formatted text response listing available tools.
    if (name === "xero_navigate") {
      const { domain } = args as { domain: Domain };
    
      const domainTools = getDomainTools(domain);
      const toolSummary = domainTools
        .map((t) => `- ${t.name}: ${t.description}`)
        .join("\n");
    
      return {
        content: [
          {
            type: "text",
            text: `${domainDescriptions[domain]}\n\nAvailable tools:\n${toolSummary}\n\nYou can call any of these tools directly.`,
          },
        ],
      };
    }
  • src/index.ts:195-198 (registration)
    Registration of xero_navigate in the ListTools handler. The navigateTool is included in the full list of tools returned by the server.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      const domainTools = getAllDomainTools();
      return { tools: [navigateTool, statusTool, backTool, ...domainTools] };
    });
  • Helper function used by the xero_navigate handler to retrieve domain-specific tools by domain name.
    function getDomainTools(domain: Domain): Tool[] {
      switch (domain) {
        case "contacts":
          return contactTools;
        case "invoices":
          return invoiceTools;
        case "payments":
          return paymentTools;
        case "accounts":
          return accountTools;
        case "reports":
          return reportTools;
      }
    }
  • Domain descriptions used by the xero_navigate handler to describe each domain in its response.
    const domainDescriptions: Record<Domain, string> = {
      contacts:
        "Contact management - list, get, create, and search contacts (customers and suppliers)",
      invoices:
        "Invoice management - list, get, create invoices and update their status",
      payments:
        "Payment management - list, get, and create payments against invoices",
      accounts:
        "Chart of accounts - list and view account details by type and class",
      reports:
        "Financial reports - profit & loss, balance sheet, aged receivables, and aged payables",
    };
Behavior5/5

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

Given no annotations, the description fully bears the burden and clearly indicates it's non-destructive, returns information, and is optional, with no contradictions.

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?

Two concise sentences with front-loaded purpose and a behavioral note, no wasted text.

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

Completeness5/5

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

For a simple discovery tool with one parameter and no output schema, the description covers purpose, return type, and usage context sufficiently.

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 detailed enum description, so the tool description adds no additional parameter information beyond what's already in the schema.

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 it's a discovery tool that returns tool names and descriptions for a selected domain, distinguishing it from sibling tools which perform actual operations.

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?

It explicitly states it's a help/discovery aid and not a prerequisite, implying it should be used when exploring available tools, though it lacks explicit when-to-use vs alternatives.

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