falladviser-v2-mcp

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation5/5
Each tool has a well-defined and distinct purpose covering different areas of UK personal finance: ISA/CGT optimization, inheritance tax, pension allowances, pension projections, portfolio analysis, and total tax calculation. No two tools overlap in functionality.
Naming Consistency5/5
All tools use lowercase snake_case with descriptive names that clearly indicate their function (e.g., bed_and_isa, iht_estimate, pension_annual_allowance). The naming convention is consistent across the entire set.
Tool Count5/5
With 6 tools, the set is well-scoped for a financial advisory MCP. Each tool addresses a core aspect of UK financial planning without being overly granular or too sparse.
Completeness4/5
The tools cover major areas like tax, pensions, inheritance, and portfolio analysis. However, there are minor gaps such as no tool for state pension or detailed retirement income modeling, but the set is functional for common advisory scenarios.
Average 3.2/5 across 6 of 6 tools scored. Lowest: 2.6/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 3 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description alone must disclose behavior. It vaguely hints at calculations (compound growth, annuity, drawdown) but lacks specifics on assumptions, return values, or side effects. For a financial projection tool, 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 extremely brief, almost a tagline. While it wastes no words, it sacrifices clarity and completeness. Important information is omitted for brevity.
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 5 parameters and no output schema or annotations, the description is incomplete. It does not explain what the projection returns (e.g., annual values, final pot, depletion year), or handle edge cases like missing optional parameters. Sibling tools suggest a financial planning suite, but this tool's specific contribution is unclear.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must explain parameters. It mentions 'compound growth', 'annuity', and 'drawdown-years' which loosely map to growthRate, annuityRate, and years, but does not clarify units, meaning of 'years' (contribution years? drawdown years?), or the role of annualContrib. The defaults for growthRate and annuityRate are not explained.
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 it's a pension projection using compound growth, annuity, and drawdown-years. It gives a specific verb and resource, but does not differentiate from sibling tools like 'pension_annual_allowance' or 'portfolio_analysis'.
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 on when to use this tool versus alternatives. It does not mention prerequisites, context, or exclusions. Sibling tools handle related but distinct tasks, but no comparisons are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must convey behavioral traits. It mentions the reform details but does not disclose whether the tool is a read-only calculation, mutates data, or has side effects. The lack of information on input handling (e.g., gifts, liabilities) and output format diminishes transparency.
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 two sentences, no redundant words. However, the second sentence 'Applies NRB (£325k) + RNRB (£175k, if main home)' is slightly cryptic and could be more explanatory. Overall concise.
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?
The tool performs a complex IHT calculation with a specific reform, yet the description lacks details on computation method, assumptions, or output. With no output schema and only 33% parameter coverage, the description fails to provide sufficient context for correct usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers 6 parameters but only describes 2 (aprAssets, bprAssets) with inline descriptions (33% coverage). The tool description adds no parameter-level details beyond mentioning NRB and RNRB, which do not correspond to any parameter name. Users may not understand how liabilities, otherAssets, etc., are used.
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?
Description clearly states the tool calculates an inheritance tax estimate after a specific reform. It mentions key allowances (NRB, RNRB) and the combined cap, making the scope clear. The sibling tools are unrelated (pension, ISA, etc.), so differentiation is implicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives. The context of siblings suggests it's for IHT estimation, but no exclusions or prerequisites are provided. The description implies use for post-2026 scenarios but does not specify when other IHT tools might be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden but only discloses the tax year and region dependency. It does not mention limitations, assumptions (e.g., no student loan deductions), or behavioral traits like whether it returns a breakdown or total only. The term 'facade' is ambiguous.
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?
A single sentence with no redundancy, front-loaded with the tool's core purpose. Every element (year, tax components, region) earns its place.
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 no output schema and six parameters, the description omits critical details: return format, example usage, and whether the tool handles edge cases. It is incomplete for a calculation tool of this complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds context by mapping parameters to tax components (e.g., income to income tax, cgtRealised to CGT), but it does not explain rentalIncome or savingsInterest, which lack schema descriptions. Schema coverage is ~67%, and the description partially compensates.
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 computes a UK total tax figure for 2025-26, listing included taxes. This is specific and resource-oriented, but it does not explicitly differentiate itself from sibling tools like iht_estimate or pension_annual_allowance, relying on context clues from the sibling list.
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, nor does it mention any prerequisites or exclusions. The sibling list is provided but not referenced, leaving the agent to infer usage without explicit direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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. It mentions drift and concentration warnings but does not explain what these entail, whether the tool is read-only, or what permissions are needed. Behavioral insights are limited.
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 a single concise sentence that front-loads the key action. However, the phrasing is dense and could be slightly improved with clearer structure or bullet points for readability.
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?
With no output schema, the description fails to detail return values such as the format of drift and concentration warnings. It covers the tool's core purpose and parameters adequately but lacks output specifics, making it incomplete for understanding all facets of tool usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It adds meaning to `attitudeToRisk` by linking it to ATR target (1-7), but does not elaborate on the `holdings` parameter structure beyond the schema. It provides some context but not enough for full parameter understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool performs portfolio bucketing (equity/bond/cash/alt) and generates drift and concentration warnings relative to an ATR target (1-7). It uses specific verbs and resources, and distinguishes itself from sibling tools which focus on tax and pension estimates.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for portfolio analysis, but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention prerequisites or alternatives among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the calculation logic and constraints (taper, floor, carry-forward), which adds behavioral context beyond the parameter names. However, it does not specify the return value or side effects, and no annotations exist to fill gaps.
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?
Two dense sentences with no extraneous words. Key information is front-loaded and efficiently communicated.
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 complexity of the tool (taper and carry-forward) and lack of output schema, the description is incomplete. It does not describe the output format, return type, or edge cases (e.g., when floor applies).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 33% (priorYears has an explanation). The description adds meaning to adjustedIncome and thresholdIncome by referencing them in the taper formula, but does not fully define each parameter or how they are used, leaving gaps.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool calculates the pension annual allowance taper and carry-forward, specifying the formula and rules. It distinguishes itself from sibling tools which cover ISAs, inheritance tax, projections, portfolio analysis, and overall tax.
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 explicit guidance on when to use this tool versus alternatives. The description only explains the calculation, implying its use for pension allowance but does not provide context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/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. It reveals the tool's advisory nature ('suggestions') and constraints (CGT allowance), but it does not clarify whether it executes trades or only calculates, nor does it mention authorization or destructive behavior. The description is partially transparent.
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 sentence that conveys the core purpose without fluff. It is front-loaded with key information and earns its place.
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?
The description covers the essential purpose but lacks details on output format, constraints (e.g., maximum recommendations), and behavioral nuances. With no output schema and moderate complexity, it is adequate but not comprehensive.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, and the description does not explain any of the three parameters ('holdings', 'isaUsedThisYear', 'cgtRealisedThisYear'). Parameter names are somewhat self-explanatory, but the description fails to add meaning, e.g., clarifying format of 'holdings' array or units of numbers.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/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: 'CGT-aware Bed & ISA suggestions — moves GIA/taxable holdings into unused ISA allowance while staying within CGT allowance.' It identifies the specific verb ('suggestions'), resource ('Bed & ISA'), and scope (within CGT allowance), distinguishing it from sibling tools like iht_estimate or total_tax.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use (when optimizing GIA holdings for ISA and CGT allowances) but does not explicitly state when not to use or mention alternatives. However, it provides enough context through the phrase 'moves GIA/taxable holdings into unused ISA allowance' to guide selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![falladviser-v2-mcp MCP server](https://glama.ai/mcp/servers/sjgant80-hub/falladviser-v2-mcp/badges/card.svg)](https://glama.ai/mcp/servers/sjgant80-hub/falladviser-v2-mcp)

Score Badge

Copy to your README.md:

[![falladviser-v2-mcp MCP server](https://glama.ai/mcp/servers/sjgant80-hub/falladviser-v2-mcp/badges/score.svg)](https://glama.ai/mcp/servers/sjgant80-hub/falladviser-v2-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/sjgant80-hub/falladviser-v2-mcp'

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