Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

xero_accounts

Read-onlyIdempotent

Fetch the chart of accounts from Xero to categorize financial transactions and support accounting workflows.

Instructions

Get chart of accounts from Xero.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "xero_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
tenant_idNo
access_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not mention the required authentication or tenant scoping despite access_token and tenant_id being parameters, and says nothing about pagination or result scope.

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?

One short sentence, front-loaded and free of waste. It is slightly too terse given the presence of three parameters that need explanation, but it is not padded.

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?

With three undocumented parameters, no output schema, and an authenticated open-world API, the description omits operational essentials such as which credentials are needed and whether the returned list is filtered by tenant. It is under-specified for a tool of this shape.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and does not. The 'type' parameter is ambiguous (account class? account type?); the description doesn't say it filters, nor what values it accepts. The auth/tenant parameters go entirely unmentioned.

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 names a specific verb and resource: 'Get chart of accounts from Xero.' An agent can understand what data is returned without opening the schema. It gains no differentiation from siblings, though the resource name is distinct enough in practice.

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?

There is no guidance on when to use this versus sibling tools like xero_invoices or xero_contacts, no prerequisites, and no exclusions. The agent is left to infer that this is the accounts-listing call for the Xero integration.

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