Skip to main content
Glama
dsfaccini

Siigo MCP Server

by dsfaccini
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_product

Retrieve detailed product information including prices and taxes from the Siigo Colombian invoicing system by providing the product's unique identifier.

Instructions

Get a product by ID.

Args: product_id: The product's GUID

Returns the full product details including prices and taxes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/siigo_mcp/tools/products.py:37-47 (handler)
    The @mcp.tool decorated handler function that implements the get_product tool logic by retrieving a product by ID from the Siigo API.
    @mcp.tool
async def get_product(ctx: Context, product_id: str) -> dict[str, Any]:
    """Get a product by ID.

    Args:
        product_id: The product's GUID

    Returns the full product details including prices and taxes.
    """
    return await get_client(ctx).get(f"/products/{product_id}")
  • src/siigo_mcp/tools/discovery.py:87-87 (registration)
    Registration mapping the tool name 'get_product' to the products.get_product function in the lazy-loaded tool functions dictionary.
    "get_product": products.get_product,
  • src/siigo_mcp/tools/discovery.py:33-33 (schema)
    Discovery schema entry for 'get_product' in TOOL_INDEX, used by list_siigo_tools to describe the tool's name, category, and summary.
    {"name": "get_product", "category": "products", "summary": "Get a product by ID"},

Tool Definition Quality

B3.3/5.0
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 of behavioral disclosure. It states the tool returns product details but doesn't mention whether it's a read-only operation, requires authentication, has rate limits, or handles errors. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, followed by brief but clear sections for arguments and returns. Every sentence earns its place without redundancy, making it efficiently structured and easy to parse.

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 low complexity (one parameter) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers the purpose, parameter semantics, and return scope adequately, though it lacks behavioral details that annotations would typically provide.

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 for the single parameter 'product_id' by specifying it's a GUID, which clarifies the expected format beyond the schema's generic string type. With 0% schema description coverage, this compensates well, though it doesn't detail validation rules or examples.

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 ('product by ID'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from its sibling 'list_products', which retrieves multiple products rather than a single one by ID.

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_products' or other sibling tools. It lacks context about prerequisites, such as needing a valid product ID, or exclusions, leaving the agent to infer usage based on the tool name alone.

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