Skip to main content
Glama
dsfaccini

Siigo MCP Server

by dsfaccini
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_invoice

Retrieve detailed invoice information by ID from the Siigo Colombian electronic invoicing system, including items, taxes, and payment details.

Instructions

Get an invoice by ID.

Args: invoice_id: The invoice's GUID

Returns the full invoice details including items, taxes, and payments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
invoice_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/siigo_mcp/tools/invoices.py:42-52 (handler)
    The core handler function implementing the 'get_invoice' MCP tool. It fetches the invoice details from the Siigo API using the provided invoice_id.
    @mcp.tool
async def get_invoice(ctx: Context, invoice_id: str) -> dict[str, Any]:
    """Get an invoice by ID.

    Args:
        invoice_id: The invoice's GUID

    Returns the full invoice details including items, taxes, and payments.
    """
    return await get_client(ctx).get(f"/invoices/{invoice_id}")
  • src/siigo_mcp/tools/discovery.py:93-93 (registration)
    Registers the 'get_invoice' tool in the dynamic tool loader by mapping the name to its implementation in invoices module.
    "get_invoice": invoices.get_invoice,
  • src/siigo_mcp/tools/discovery.py:39-39 (schema)
    Static tool index entry providing metadata (name, category, summary) for discovery of the 'get_invoice' tool.
    {"name": "get_invoice", "category": "invoices", "summary": "Get an invoice by ID"},

Tool Definition Quality

B3.2/5.0
Behavior2/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 states the tool returns invoice details but doesn't mention whether it's a read-only operation, requires authentication, has rate limits, or handles errors. This leaves significant gaps for a tool that likely accesses sensitive financial data.

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 well-structured and front-loaded with the core purpose, followed by clear sections for arguments and returns. Every sentence adds value without redundancy, 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's moderate complexity (single parameter, no nested objects) and the presence of an output schema, the description covers the basics but lacks behavioral context. It explains what the tool does and returns but misses details like permissions, error handling, or sibling tool differentiation, which are important for completeness.

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 description adds meaningful context beyond the schema, specifying that 'invoice_id' is a GUID and explaining what the tool returns. Since schema description coverage is 0% and there's only one parameter, this adequately compensates, though it could provide more detail about the GUID format.

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 tool's purpose with a specific verb ('Get') and resource ('invoice by ID'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'list_invoices' or 'get_invoice_pdf', which would be needed for a perfect score.

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 like 'list_invoices' or 'get_invoice_pdf'. It mentions retrieving by ID but doesn't specify prerequisites, exclusions, or contextual usage scenarios.

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