Skip to main content
Glama
norman-finance

Norman Finance MCP Server

Official
by norman-finance
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_vat_next_report

Retrieve VAT amount data for the upcoming report period using the Norman Finance MCP Server. Streamline tax preparation and financial planning with accurate VAT insights.

Instructions

Get the VAT amount for the next report period.

Returns:
    VAT next report amount data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • norman_mcp/tools/taxes.py:283-302 (handler)
    The handler function for the 'get_vat_next_report' tool. It retrieves the VAT amount for the next report period by making an API request using the company's ID.
    @mcp.tool()
async def get_vat_next_report(ctx: Context) -> Dict[str, Any]:
    """
    Get the VAT amount for the next report period.
    
    Returns:
        VAT next report amount data
    """
    api = ctx.request_context.lifespan_context["api"]
    company_id = api.company_id
    
    if not company_id:
        return {"error": "No company available. Please authenticate first."}
    
    vat_url = urljoin(
        config.api_base_url,
        f"api/v1/companies/{company_id}/vat-next-report-amount/"
    )
    
    return api._make_request("GET", vat_url)
  • norman_mcp/server.py:330-330 (registration)
    Call to register_tax_tools which registers the get_vat_next_report tool along with other tax tools on the MCP server.
    register_tax_tools(server)

Tool Definition Quality

C2.9/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 states the tool 'Returns: VAT next report amount data', which hints at read-only behavior but doesn't clarify aspects like authentication needs, rate limits, error handling, or data freshness. For a 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.

Conciseness3/5

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

The description is brief with two sentences, but it could be more front-loaded. The first sentence states the purpose clearly, but the second ('Returns: VAT next report amount data') is somewhat redundant and doesn't add significant value. Overall, it's concise but not optimally structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'VAT next report amount data' includes (e.g., format, units, or structure), nor does it cover behavioral aspects like permissions or side effects. For a tool in a financial context, this leaves critical gaps.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param details, which is appropriate. A baseline of 4 is applied since the schema fully handles parameters, and the description doesn't introduce confusion.

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 the VAT amount for the next report period.' It specifies the verb ('Get') and resource ('VAT amount'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from siblings like 'get_tax_report' or 'get_company_tax_statistics', which prevents a perfect score.

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 prerequisites, context (e.g., related to tax reporting cycles), or comparisons to sibling tools like 'get_tax_report'. This lack of usage context leaves the agent with minimal direction.

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