Skip to main content
Glama

get_customer

Retrieve detailed customer information including contacts and addresses by providing the customer's unique identifier through the Siigo MCP Server.

Instructions

Get a customer by ID.

Args: customer_id: The customer's GUID

Returns the full customer details including contacts and addresses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function implementing the get_customer tool. It uses the Siigo API client to fetch customer details by ID.
    @mcp.tool
    async def get_customer(ctx: Context, customer_id: str) -> dict[str, Any]:
        """Get a customer by ID.
    
        Args:
            customer_id: The customer's GUID
    
        Returns the full customer details including contacts and addresses.
        """
        return await get_client(ctx).get(f"/customers/{customer_id}")
  • Discovery schema entry for the get_customer tool, providing name, category, and summary.
    {"name": "get_customer", "category": "customers", "summary": "Get a customer by ID"},
  • Registration mapping for customer tools, including get_customer, used in lazy loading for dynamic tool execution.
    # 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,
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 it 'Returns the full customer details including contacts and addresses,' which gives some output context, but lacks details on permissions, error handling, rate limits, or whether it's a read-only operation. For a retrieval tool with zero annotation coverage, this is insufficient.

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 concise, using a clear title sentence followed by bullet points for arguments and returns. Every sentence adds value without redundancy, making it easy to scan and understand quickly.

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 simplicity (single parameter, has output schema), the description covers the basics but lacks depth. It explains the parameter and return data, but without annotations or detailed behavioral context, it's only minimally adequate for an agent to use it correctly in varied scenarios.

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 input schema by specifying that 'customer_id' is a 'GUID' and clarifying what data is returned. Since schema description coverage is 0% and there's only one parameter, this adequately compensates, though it could include format examples or constraints.

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 ('customer by ID'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from its sibling 'list_customers', which retrieves multiple customers 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_customers' or other retrieval tools. It mentions the required parameter but offers no context about prerequisites, error conditions, or typical use cases.

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