Skip to main content
Glama

BRAINIAC Bank, Credit Union & Charity Registries

Look up a charity in England and Wales

registries_uk-charity-lookup
Read-onlyIdempotent

Find a charity on the Charity Commission register for England and Wales by registered number or name from a vendored charity-level subset of the register extract. Removed charities are reported, not missed. Price $0.03 USDC. POST /api/v1/registries/uk-charity-lookup. An unpaid call returns the x402 payment terms and does not run.

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": "registries_uk-charity-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoname, string, length 2 to 200. Optional.
limitNolimit, integer, from 1 to 50. Required.
charityNumberNocharityNumber, integer, from 200000 to 9999999. Optional.
includeLinkedNoincludeLinked, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
snapshotNosnapshot. Object.
limitationsNolimitations. Array.
totalCandidatesNototalCandidates. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the payment model ($0.03 USDC), the transport (POST /api/v1/registries/uk-charity-lookup), and crucially the unpaid-call behavior ("returns the x402 payment terms and does not run"). It also flags that removed charities are reported rather than missed, which is a real data-completeness trait an agent could otherwise misread as a failure. Still silent on pagination behavior and how partial-name matches are ranked.

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?

Four short sentences with the purpose and data-source caveat front-loaded, followed by the commercial and failure-mode facts. The literal endpoint string is slightly redundant filler, but nothing else is wasted and each sentence carries distinct information.

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

Completeness4/5

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

With an output schema present, return values need not be explained, and the description covers the two things an agent genuinely cannot get from structured fields: payment gating and the removed-charity reporting behavior. The remaining gap is the extent of the vendored subset and default result paging, which affect interpretation of a partial result set.

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 100%, so the four parameters are already documented in structured form, which sets the baseline at 3. The description adds the useful framing that number and name are alternative lookup keys but says nothing about `limit` or `includeLinked` (what linked entities mean or when to enable them).

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 ("Find a charity on the Charity Commission register for England and Wales"), names the two lookup keys (registered number or name), and scopes the data source ("vendored charity-level subset of the register extract"). The jurisdiction and registry make it unambiguously distinct from the bank and credit-union lookup siblings.

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?

Usage is implied by the named lookup keys rather than stated: an agent can infer it should call this when it has a charity number or name. There is no explicit when-not guidance, no statement about what to do if no match is returned, and no mention of how it relates to the sibling registry lookups.

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