Skip to main content
Glama

get_taxes

Retrieve configured tax information from Siigo to apply correct tax IDs when creating invoices or products in Colombian electronic invoicing.

Instructions

Get all configured taxes in the Siigo account.

Returns a list of taxes with their IDs, names, and percentages. Use these tax IDs when creating invoices or products.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_taxes' tool, decorated with @mcp.tool. It retrieves all configured taxes from the Siigo API endpoint "/taxes" using the authenticated client.
    @mcp.tool
    async def get_taxes(ctx: Context) -> list[dict[str, Any]]:
        """Get all configured taxes in the Siigo account.
    
        Returns a list of taxes with their IDs, names, and percentages.
        Use these tax IDs when creating invoices or products.
        """
        return await get_client(ctx).get("/taxes")
  • Registration mapping for 'get_taxes' in the lazy/dynamic tool execution system, linking the tool name to the actual function reference.get_taxes.
    "get_taxes": reference.get_taxes,
  • Tool discovery index entry (schema metadata) defining the 'get_taxes' tool's name, category ('reference'), and one-line summary.
    {"name": "get_taxes", "category": "reference", "summary": "Get all configured taxes"},
  • Import of the 'reference' module in server.py (non-lazy mode), which triggers auto-registration of the 'get_taxes' tool via its @mcp.tool decorator.
    from siigo_mcp.tools import reference  # noqa: E402, F401
    from siigo_mcp.tools import customers  # noqa: E402, F401
    from siigo_mcp.tools import products  # noqa: E402, F401
    from siigo_mcp.tools import invoices  # noqa: E402, F401
    from siigo_mcp.tools import credit_notes  # noqa: E402, F401
    from siigo_mcp.tools import journals  # noqa: E402, F401
  • Helper function get_client(ctx) used by the get_taxes handler to obtain an authenticated SiigoClient instance for API calls.
    def get_client(ctx: Context) -> SiigoClient:
        """Get Siigo client - from headers (HTTP mode) or env vars (stdio mode)."""
        if _transport == "http":
            if not ctx.request_context:
                raise ValueError("No request context available in HTTP mode")
            headers = ctx.request_context.request.headers
            username = headers.get("x-siigo-username")
            access_key = headers.get("x-siigo-access-key")
            partner_id = headers.get("x-siigo-partner-id")
            if not all([username, access_key, partner_id]):
                raise ValueError(
                    "Missing required headers: x-siigo-username, x-siigo-access-key, x-siigo-partner-id"
                )
            client_class = _get_client_class()
            return client_class(username=username, access_key=access_key, partner_id=partner_id)
    
        return _get_global_client()
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the return format ('list of taxes with their IDs, names, and percentages') and hints at a read-only operation ('Get'), but does not disclose other behavioral traits such as authentication needs, rate limits, or error handling. The description adds some context but is incomplete for a tool with no annotations.

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 front-loaded with the core purpose in the first sentence, followed by additional context in a second sentence. Both sentences earn their place by providing essential information without redundancy, making it efficiently structured and appropriately sized.

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

Completeness4/5

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

Given the tool's complexity (simple read operation with 0 parameters), the description is mostly complete: it states the purpose, return format, and usage context. With an output schema present, it does not need to explain return values in detail. However, it lacks details on behavioral aspects like authentication or error handling, which are relevant for a tool with no annotations, leaving a minor gap.

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 tool has 0 parameters, and the schema description coverage is 100%, so no parameter information is needed. The description does not add parameter semantics, but this is appropriate given the lack of parameters. A baseline score of 4 is applied as it compensates adequately for the zero-parameter case.

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 specific action ('Get all configured taxes') and resource ('in the Siigo account'), distinguishing it from sibling tools like get_customer or get_product. It explicitly mentions the scope ('all configured taxes') and the system context ('Siigo account'), providing a precise purpose.

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

Usage Guidelines4/5

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

The description includes a clear usage context by stating 'Use these tax IDs when creating invoices or products,' which indicates when this tool's output is applicable. However, it does not explicitly differentiate when to use this tool versus alternatives (e.g., no mention of sibling tools like get_document_types or get_payment_types for other configuration data), so it lacks explicit exclusions or named alternatives.

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