Skip to main content
Glama

xero_book_depreciation

Records depreciation journal entries for fixed assets in Xero, automating the book depreciation process.

Instructions

Xero connector operation book_depreciation (platform tool xero.book_depreciation).

Routes through /api/tools/invoke under your JWT, tenant, and company scope.

Args: arguments: JSON string of arguments for the connector operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo{}

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description should disclose behavioral traits but only provides routing infrastructure details. It does not indicate that this is a write operation that modifies financial records, nor does it warn about consequences or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but not optimally structured. It includes unnecessary routing details (JWT, tenant, company scope) that do not aid tool selection, while omitting critical functional information. It is concise in word count but wasteful in content.

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

Completeness1/5

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

Given the financial nature of depreciation and the presence of an output schema, the description is severely lacking. It fails to explain the tool's effect, required inputs, output, or safety considerations, making it essentially unusable for an AI agent.

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

Parameters1/5

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

The sole parameter 'arguments' is a JSON string with no schema description (0% coverage). The description only says it contains 'arguments for the connector operation', adding no structure, required keys, or examples. This leaves the agent completely unable to form a correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only restates the tool name as 'Xero connector operation book_depreciation' without explaining what booking depreciation entails. It does not clarify the specific accounting action, such as recording depreciation for an asset, and offers no distinction from sibling tools like xero_create_asset or xero_dispose_asset.

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 guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context (e.g., existing asset), or when not to use it, leaving the agent without any decision-making criteria.

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/RPasquale/lightbulb-mcp'

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