Skip to main content
Glama

get_uk_fca_coverage

Read-only

Use when assessing FCA model risk management compliance readiness or benchmarking an AI governance program against UK regulatory expectations. Returns coverage across 13 control objectives from FCA Policy Statement PS7/24. Example: PS7/24 requires documented model validation methodology, ongoing performance monitoring, and board-level model risk appetite statement — gaps in any of the three trigger supervisory concern. Source: FCA Policy Statement PS7/24. $0.50 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_uk_fca_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
nistFunctionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuine context the annotations do not: the 13-control-objective scope, the upstream source document, and a per-call price of $0.50 USDC, which is important operational information for an agent deciding whether to invoke.

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?

Three tight sentences: usage condition first, return scope second, concrete example with an illustration of a gap condition third, plus source and price. Every sentence earns its place and the most decision-relevant information is front-loaded.

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 single optional parameter and no output schema, the description covers purpose, scope, source, and cost but leaves the return structure (13 objectives in what form) and the filter parameter entirely unexplained. Adequate to decide whether to call, insufficient to call it correctly.

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% and the description never mentions the single optional parameter nistFunction or its enum values (GOVERN, MAP, MEASURE, MANAGE). An agent cannot tell from the description that results can be scoped to a NIST AI RMF function, so the description fails to compensate for the schema gap.

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?

States a specific verb and resource: returns coverage across 13 control objectives from FCA Policy Statement PS7/24, framed for model risk management / AI governance compliance. The regulator-specific framing (FCA, UK, PS7/24) implicitly separates it from other regulatory-coverage siblings such as get_eu_ai_act_coverage.

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?

Opens with explicit when-to-use guidance: assessing FCA model risk management compliance readiness or benchmarking an AI governance program against UK regulatory expectations. It gives no when-not-to-use condition or named alternative, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources