Skip to main content
Glama

xero_back

Returns to domain selection in Xero MCP Server, enabling you to choose a different domain for your tasks.

Instructions

Return to domain selection (no-op in flattened mode). All tools are always available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the xero_back tool - returns a no-op message indicating all tools are always available in flattened mode.
    if (name === "xero_back") {
      return {
        content: [
          {
            type: "text",
            text: "All tools are always available in flattened mode. Use xero_navigate to discover tools by domain: contacts, invoices, payments, accounts, reports",
          },
        ],
      };
    }
  • Schema/tool definition for xero_back - a no-op compatibility tool with no required inputs.
    const backTool: Tool = {
      name: "xero_back",
      description:
        "Return to domain selection (no-op in flattened mode). All tools are always available.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    };
  • src/index.ts:195-198 (registration)
    Registration of xero_back in the tool listing returned by ListToolsRequestSchema handler.
    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?

Discloses no-op behavior in flattened mode, which is helpful. However, without annotations, it does not fully detail behavior in non-flattened mode or any side effects, leaving some ambiguity.

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 sentences, no wasted words. Front-loaded with purpose.

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?

Explains core behavior but does not elaborate on what 'domain selection' means or how this fits into multi-step workflows. Agent may need more context to decide when to invoke this tool.

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?

No parameters exist, so schema coverage is 100%. Description adds no parameter info, but baseline for zero parameters is 4.

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?

Description clearly states it returns to domain selection and explains behavior in flattened mode. It differentiates from sibling tools by being a navigation action, but 'domain selection' could be more explicitly defined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage context (return to domain selection) and notes flattened mode behavior, but does not explicitly compare to alternatives like xero_navigate or specify when to use this versus other navigation tools.

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