Skip to main content
Glama
deenesjakoruzh
norman-finance

Norman Finance MCP Server

Official
by norman-finance
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

list_tax_reports

Access and retrieve all available tax reports for accounting and tax filing needs using Norman Finance MCP Server. Simplify financial workflows with integrated API capabilities.

Instructions

List all available tax reports.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • norman_mcp/tools/taxes.py:19-26 (handler)
    The main handler function for the 'list_tax_reports' tool, decorated with @mcp.tool() to register it. Makes a GET request to retrieve the list of tax reports.
    @mcp.tool()
async def list_tax_reports(ctx: Context) -> Dict[str, Any]:
    """List all available tax reports."""
    api = ctx.request_context.lifespan_context["api"]
    
    taxes_url = urljoin(config.api_base_url, "api/v1/taxes/reports/")
    
    return api._make_request("GET", taxes_url)
  • norman_mcp/server.py:330-330 (registration)
    Top-level registration call that invokes register_tax_tools(server), which defines and registers the list_tax_reports tool.
    register_tax_tools(server)
  • norman_mcp/server.py:18-18 (registration)
    Import of the register_tax_tools function used to register tax-related tools including list_tax_reports.
    from norman_mcp.tools.taxes import register_tax_tools

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, if it requires authentication, how results are returned (e.g., pagination), or any rate limits, leaving significant gaps for a tool that likely interacts with sensitive tax data.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for a simple listing tool, making it easy for an agent to parse 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 (0 parameters, no output schema), the description is minimally adequate but lacks depth. Without annotations or output schema, it should ideally clarify what 'list' entails (e.g., format, scope) to be more complete, especially in a context with many sibling tools.

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 with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, earning a baseline score of 4 for not introducing unnecessary complexity.

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 ('List') and resource ('tax reports'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_tax_report' or 'list_tax_settings', which would require more specificity to earn a 5.

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 'get_tax_report' or 'list_tax_settings'. It lacks context about prerequisites, timing, or exclusions, leaving the agent to infer usage from the 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

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