Skip to main content
Glama

get_credit_note

Retrieve detailed credit note information by ID from the Siigo electronic invoicing system. Use this tool to access specific credit note data for accounting or customer service purposes.

Instructions

Get a credit note by ID.

Args: credit_note_id: The credit note's GUID

Returns the full credit note details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
credit_note_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function decorated with @mcp.tool that implements the logic to fetch a credit note by ID from the Siigo API.
    @mcp.tool
    async def get_credit_note(ctx: Context, credit_note_id: str) -> dict[str, Any]:
        """Get a credit note by ID.
    
        Args:
            credit_note_id: The credit note's GUID
    
        Returns the full credit note details.
        """
        return await get_client(ctx).get(f"/credit-notes/{credit_note_id}")
  • Registration of the get_credit_note tool (and related credit notes tools) in the lazy-loading tool functions dictionary.
    "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,
  • Schema-like entry in TOOL_INDEX providing name, category, and summary for discovery of the get_credit_note tool.
    {"name": "get_credit_note", "category": "credit_notes", "summary": "Get a credit note by ID"},
  • Import of the credit_notes module containing the get_credit_note handler.
    from siigo_mcp.tools import reference, customers, products, invoices, credit_notes, journals
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 retrieves data ('Get'), implying it's likely read-only, but doesn't confirm this or address other aspects like authentication needs, error handling, rate limits, or what 'full credit note details' entails. The description is minimal and lacks behavioral context beyond the basic operation.

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 appropriately sized and front-loaded. The first sentence ('Get a credit note by ID.') directly states the purpose, followed by a brief 'Args' section and a return statement. Every sentence adds value without redundancy, making it efficient and well-structured.

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 (single parameter, no annotations, but has an output schema), the description is reasonably complete. It covers the basic operation and parameter semantics. The presence of an output schema means the description doesn't need to detail return values, but it could improve by addressing behavioral aspects like read-only confirmation or error cases.

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 semantics beyond the input schema. The schema has 0% description coverage and only defines 'credit_note_id' as a string. The description specifies that 'credit_note_id' is 'The credit note's GUID', clarifying its format and purpose. With one parameter and low schema coverage, this compensation is effective, though not exhaustive.

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: 'Get a credit note by ID' specifies the verb ('Get') and resource ('credit note'), and 'Returns the full credit note details' elaborates on the outcome. However, it doesn't explicitly differentiate from sibling tools like 'list_credit_notes' (which likely lists multiple notes) or 'get_credit_note_pdf' (which retrieves a PDF version), missing full sibling distinction.

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 doesn't mention sibling tools such as 'list_credit_notes' for browsing or 'get_credit_note_pdf' for PDF retrieval, nor does it specify prerequisites like needing a specific credit note ID. Usage is implied but not explicitly stated.

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