Skip to main content
Glama

xero_status

Check the status of your Xero credentials and view available domains for connection. Ensures your setup is valid before proceeding with accounting operations.

Instructions

Show credentials status and available domains

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the xero_status tool. Checks credentials status (checks for XERO_ACCESS_TOKEN env var) and returns a text response listing the available domains.
    if (name === "xero_status") {
      const credStatus = process.env.XERO_ACCESS_TOKEN
        ? `Configured (tenant: ${process.env.XERO_TENANT_ID || "env-based"})`
        : "NOT CONFIGURED - Please set environment variables";
    
      return {
        content: [
          {
            type: "text",
            text: `Xero MCP Server Status\n\nCredentials: ${credStatus}\nAvailable domains: contacts, invoices, payments, accounts, reports\n\nAll tools are available at all times. Use xero_navigate to discover tools by domain.`,
          },
        ],
      };
    }
  • The tool schema definition for xero_status. Defines the tool name, description, and empty input schema (no parameters required).
    const statusTool: Tool = {
      name: "xero_status",
      description: "Show credentials status and available domains",
      inputSchema: {
        type: "object",
        properties: {},
      },
    };
  • src/index.ts:195-198 (registration)
    Registration of xero_status in the ListTools handler. The statusTool is included in the tools list returned by the ListToolsRequestSchema handler, making it available to MCP clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      const domainTools = getAllDomainTools();
      return { tools: [navigateTool, statusTool, backTool, ...domainTools] };
    });
Behavior3/5

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

The description implies a read-only operation by stating 'show', which is appropriate for a status check. However, it lacks details about side effects, required permissions, or exactly what the status entails. With no annotations, the description carries the full burden and provides minimal behavioral context.

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 extremely concise and front-loaded, stating the core purpose in a single phrase with no unnecessary words. Every word earns its place.

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?

Given the tool has no parameters and no output schema, the description is adequate for a simple status check. However, it could provide more context, such as typical usage pattern (e.g., check before other operations) or what the output looks like. It meets the minimum viable standard.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4. The description does not need to add parameter details, and the schema already covers 100% of parameters (none).

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 tool shows credentials status and available domains, using a specific verb and resource. It distinguishes itself from sibling tools like xero_accounts_get and xero_invoices_list, which handle different entities.

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 tool versus alternatives. It's implied as a first step before other operations, but the description doesn't explicitly state this or mention any exclusions.

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