Skip to main content
Glama
norman-finance

Norman Finance MCP Server

Official
by norman-finance
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_clients

Retrieve a detailed list of all clients for your company using Norman Finance MCP Server. Simplify financial workflows by accessing client details for accounting and tax filing purposes.

Instructions

Get a list of all clients for the company.

Returns:
    List of clients with their details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • norman_mcp/tools/clients.py:14-36 (handler)
    The main handler function for the 'list_clients' MCP tool. It uses the @mcp.tool() decorator and implements the logic to fetch clients from the Norman API for the authenticated company.
    @mcp.tool()
async def list_clients(
    ctx: Context
) -> Dict[str, Any]:
    """
    Get a list of all clients for the company.
    
    Returns:
        List of clients with their details
    """
    api = ctx.request_context.lifespan_context["api"]
    company_id = api.company_id
    
    if not company_id:
        return {"error": "No company available. Please authenticate first."}
    
    clients_url = urljoin(
        config.api_base_url, 
        f"api/v1/companies/{company_id}/clients/"
    )
    
    return api._make_request("GET", clients_url)
  • norman_mcp/server.py:328-328 (registration)
    Registration of client tools (including list_clients) by calling register_client_tools on the MCP server instance.
    register_client_tools(server)
  • norman_mcp/tools/clients.py:11-11 (registration)
    The registration function that defines and registers the list_clients tool using @mcp.tool() decorator.
    def register_client_tools(mcp):

Tool Definition Quality

B3.1/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 mentions the return type ('List of clients with their details'), which adds some value, but fails to describe critical behaviors such as pagination, sorting, filtering, rate limits, or authentication requirements. For a list operation with zero annotation coverage, this is a significant gap.

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 concise and front-loaded with the main purpose in the first sentence. The second sentence adds useful return information without redundancy. However, it could be slightly more structured by explicitly separating behavior from output.

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 (0 parameters, no output schema, no annotations), the description is minimally adequate. It states the purpose and return value, but lacks details on behavior (e.g., pagination) and usage context. For a list tool in a financial context with many siblings, more guidance would improve 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 tool has 0 parameters, and the schema description coverage is 100%, so there's no need for parameter details in the description. The description doesn't add parameter semantics, but that's acceptable here. A baseline of 4 is appropriate since no parameters exist to document.

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 verb ('Get') and resource ('list of all clients for the company'), making the purpose explicit. However, it doesn't distinguish this tool from sibling tools like 'get_client' or 'search_transactions', which might also retrieve client information in different ways.

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 when to prefer 'list_clients' over 'get_client' (for a single client) or 'search_transactions' (which might filter clients indirectly), nor does it specify prerequisites like authentication or context.

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