Skip to main content
Glama

Stratalize Intelligence

Get Uk Fca Coverage

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

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly/openWorld/non-destructive), and the description adds real context beyond them: result granularity (13 control objectives), the governing source, an illustrative requirement set, and a per-call price of $0.50 USDC. It does not describe output shape or how missing objectives are scored, but with annotations in place this is solid disclosure.

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?

Roughly four sentences, front-loaded with the usage trigger and then the return content; the requirement example and price each carry information an agent would otherwise have to guess. The example sentence is somewhat dense but not wasteful.

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 read-only retrieval tool with no output schema, the description covers source, scope, and cost well. The unaddressed nistFunction filter is the notable hole — an agent cannot predict how passing it changes the coverage report, which matters for a single-parameter tool whose only knob is undocumented.

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?

There is one optional parameter, nistFunction, with schema description coverage of 0%, and the description never mentions it. The GOVERN/MAP/MEASURE/MANAGE enum is left entirely unexplained, so an agent cannot tell whether it filters, groups, or merely labels the returned coverage.

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 — coverage across 13 control objectives from FCA Policy Statement PS7/24 — and scopes it to UK regulatory expectations, which cleanly separates it from the EU AI Act sibling. An agent knows exactly what it gets back without opening the schema.

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 an explicit 'Use when' clause naming two concrete scenarios (FCA model risk compliance readiness, benchmarking an AI governance program). No when-not conditions or named alternatives are given, keeping it short of a 5.

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