Skip to main content
Glama
Sign In
lightbulb-mcp

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

xero_agent_run_sync

Trigger a Xero data sync to update organizations, AR/AP, payroll, and ledger records.

Instructions

Trigger a Xero data sync (orgs, AR/AP, payroll, ledger).

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_agent_run_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo{}

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It only says 'Trigger a Xero data sync' without revealing whether this is synchronous or asynchronous, if it can overwrite data, or any rate limits. The behavioral impact is unspecified.

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?

The description is a single sentence that is concise and to the point. However, it could be structured into more detailed segments without losing conciseness. It earns its place but could be more informative.

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?

Given the tool triggers a sync (a complex operation with potential side effects), the description is too minimal. It does not explain the sync process, expected inputs (body content), return values (despite an output schema existing), or prerequisites like authentication state. The agent lacks context to use it reliably.

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 schema has one parameter 'body' with 0% description coverage (no parameter descriptions). The tool description does not explain what the body parameter accepts (e.g., JSON keys for sync options). The description adds no value beyond the schema's basic structure.

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 triggers a Xero data sync and specifies the scope (orgs, AR/AP, payroll, ledger). This verb+resource combination is distinct among sibling tools, which focus on individual Xero operations, not a broad sync.

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 like xero_agent_run_playbook or other Xero tools. The description lacks context about prerequisites, sync frequency, or scenarios where this sync is appropriate.

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