Skip to main content
Glama
norman-finance

Norman Finance MCP Server

Official

update_client

Modify client details in Norman Finance MCP Server, including name, type, address, contact info, and VAT number. Ensures accurate and up-to-date client records for accounting and tax processes.

Instructions

Update an existing client.

Args:
    client_id: ID of the client to update
    name: Updated client name
    client_type: Updated client type ("business" or "private")
    address: Updated client physical address
    zip_code: Updated client postal/zip code
    email: Updated client email address
    country: Updated client country code (e.g. "DE")
    vat_number: Updated client VAT number
    city: Updated client city
    phone: Updated client phone number
    
Returns:
    Updated client record

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressNo
cityNo
client_idYes
client_typeNo
countryNo
emailNo
nameNo
phoneNo
vat_numberNo
zip_codeNo

Implementation Reference

  • The main handler function for the 'update_client' tool. It updates an existing client by fetching current data, applying only the provided field updates, and sending a PATCH request to the Norman API.
    @mcp.tool()
    async def update_client(
        ctx: Context,
        client_id: str,
        name: Optional[str] = None,
        client_type: Optional[str] = None,
        address: Optional[str] = None,
        zip_code: Optional[str] = None,
        email: Optional[str] = None,
        country: Optional[str] = None,
        vat_number: Optional[str] = None,
        city: Optional[str] = None,
        phone: Optional[str] = None
    ) -> Dict[str, Any]:
        """
        Update an existing client.
        
        Args:
            client_id: ID of the client to update
            name: Updated client name
            client_type: Updated client type ("business" or "private")
            address: Updated client physical address
            zip_code: Updated client postal/zip code
            email: Updated client email address
            country: Updated client country code (e.g. "DE")
            vat_number: Updated client VAT number
            city: Updated client city
            phone: Updated client phone number
            
        Returns:
            Updated client record
        """
        api = ctx.request_context.lifespan_context["api"]
        company_id = api.company_id
        
        if not company_id:
            return {"error": "No company available. Please authenticate first."}
        
        if client_type and client_type not in ["business", "private"]:
            return {"error": "client_type must be either 'business' or 'private'"}
        
        client_url = urljoin(
            config.api_base_url, 
            f"api/v1/companies/{company_id}/clients/{client_id}/"
        )
        
        # Get current client data
        current_data = api._make_request("GET", client_url)
        
        # Update only provided fields
        update_data = {}
        if name:
            update_data["name"] = name
        if client_type:
            update_data["clientType"] = client_type
        if email:
            update_data["email"] = email
        if phone:
            update_data["phone"] = phone
        if vat_number:
            update_data["vatNumber"] = vat_number
        if address:
            update_data["address"] = address
        if zip_code:
            update_data["zipCode"] = zip_code
        if country:
            update_data["country"] = country
        if city:
            update_data["city"] = city
        
        # If no fields provided, return current data
        if not update_data:
            return {"message": "No fields provided for update.", "client": current_data}
        
        return api._make_request("PATCH", client_url, json_data=update_data)
  • Calls register_client_tools(server) which registers the update_client tool (along with other client tools) with the MCP server instance.
    register_client_tools(server)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation but doesn't mention permission requirements, whether partial updates are allowed (vs. full replacement), validation rules, error conditions, or what happens when null values are provided. The 'Returns' statement is minimal and doesn't describe the record structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (Args, Returns) and uses bullet points for parameters, making it scannable. However, the parameter list is quite long (10 items), and the opening statement is minimal without additional context about the update operation's behavior.

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?

For a mutation tool with 10 parameters, no annotations, and no output schema, the description provides good parameter documentation but lacks critical behavioral context. It doesn't explain update semantics (partial vs. full), error handling, or return value structure. The presence of sibling tools like 'create_client' and 'delete_client' suggests this is part of a CRUD system that needs more contextual explanation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides excellent parameter semantics despite 0% schema description coverage. Each of the 10 parameters is clearly documented with meaningful explanations, including the client_type enum values ('business' or 'private') and country code format example ('DE'). This fully compensates for the lack of schema descriptions.

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 action ('Update an existing client') and resource ('client'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other client-related tools like 'update_company_details' or explain how it differs from 'create_client' beyond the obvious creation vs. update 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?

No guidance is provided about when to use this tool versus alternatives. While 'update_client' is clearly for modifying existing clients, there's no mention of prerequisites (e.g., client must exist), when to use 'update_company_details' instead, or how this relates to 'delete_client' or 'get_client' workflows.

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

Related 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/norman-finance/norman-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server