Skip to main content
Glama

get_account_groups

Retrieve account groups for categorizing products or customers in Siigo's electronic invoicing system.

Instructions

Get all account groups/classifications.

Returns a list of account groups for categorizing products or customers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function decorated with @mcp.tool. It fetches account groups from the Siigo API endpoint '/account-groups' using the context client.
    @mcp.tool
    async def get_account_groups(ctx: Context) -> list[dict[str, Any]]:
        """Get all account groups/classifications.
    
        Returns a list of account groups for categorizing products or customers.
        """
        return await get_client(ctx).get("/account-groups")
  • Registration of the tool name to its handler function in the lazy-loading tool map used by dynamic execution tools.
    "get_account_groups": reference.get_account_groups,
  • Tool discovery index entry providing metadata (name, category, summary) for the get_account_groups tool.
    {"name": "get_account_groups", "category": "reference", "summary": "Get all account groups"},
  • Full function that lazily loads and maps all tools, including get_account_groups, for dynamic access.
    def _get_tool_functions() -> dict[str, Any]:
        """Lazily import and map all tool functions."""
        global _tool_functions
        if _tool_functions is not None:
            return _tool_functions
    
        from siigo_mcp.tools import reference, customers, products, invoices, credit_notes, journals
    
        _tool_functions = {
            # Reference
            "get_taxes": reference.get_taxes,
            "get_payment_types": reference.get_payment_types,
            "get_document_types": reference.get_document_types,
            "get_warehouses": reference.get_warehouses,
            "get_users": reference.get_users,
            "get_account_groups": reference.get_account_groups,
            # Customers
            "list_customers": customers.list_customers,
            "get_customer": customers.get_customer,
            "create_customer": customers.create_customer,
            "update_customer": customers.update_customer,
            "delete_customer": customers.delete_customer,
            # Products
            "list_products": products.list_products,
            "get_product": products.get_product,
            "create_product": products.create_product,
            "update_product": products.update_product,
            "delete_product": products.delete_product,
            # Invoices
            "list_invoices": invoices.list_invoices,
            "get_invoice": invoices.get_invoice,
            "create_invoice": invoices.create_invoice,
            "update_invoice": invoices.update_invoice,
            "delete_invoice": invoices.delete_invoice,
            "stamp_invoice": invoices.stamp_invoice,
            "get_stamp_errors": invoices.get_stamp_errors,
            "get_invoice_pdf": invoices.get_invoice_pdf,
            "send_invoice_email": invoices.send_invoice_email,
            "annul_invoice": invoices.annul_invoice,
            # Credit notes
            "list_credit_notes": credit_notes.list_credit_notes,
            "get_credit_note": credit_notes.get_credit_note,
            "create_credit_note": credit_notes.create_credit_note,
            "get_credit_note_pdf": credit_notes.get_credit_note_pdf,
            # Journals
            "list_journals": journals.list_journals,
            "get_journal": journals.get_journal,
            "create_journal": journals.create_journal,
        }
        return _tool_functions
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool returns a list but doesn't disclose behavioral traits like pagination, rate limits, authentication needs, or whether it's read-only. The description is minimal and misses key operational details.

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 with two sentences that directly state the action and return value. It's front-loaded with the main purpose and wastes no words, making it efficient and easy to parse.

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 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, it lacks details on usage context and behavioral transparency, which are gaps for a tool with no annotations. It's complete enough for a simple read operation but could be improved.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds value by explaining the return purpose ('for categorizing products or customers'), which provides semantic context beyond the empty schema. Baseline is high due to no parameters.

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 clearly states the verb ('Get') and resource ('account groups/classifications') with the scope 'all', making the purpose specific. It distinguishes from siblings by focusing on account groups rather than other entities like invoices or customers, though it doesn't explicitly contrast with similar tools (e.g., no direct sibling for groups).

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. It mentions the purpose but lacks context on prerequisites, timing, or comparisons with other tools, such as whether it's for setup, reporting, or categorization tasks.

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/dsfaccini/siigo-mcp'

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