Christian Background Checks Partner API

Get an error code

get_error

Read-onlyIdempotent

One error code from the error catalog: its HTTP status, what it means, what to do, and whether a retry is safe. Pass the code from a problem details body (e.g. client_not_found).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "get_error"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	The error `code`, e.g. client_not_found.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world lookup. The description adds useful behavioral context by enumerating the returned fields and specifically noting whether retry is safe, which goes beyond the annotations.

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 concise sentences, front-loaded with the catalog lookup purpose and immediately followed by the only input instruction. There is no redundant or filler wording.

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

Completeness5/5

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

For a simple one-parameter lookup with no output schema, the description is complete enough: it explains what is returned, where to get the input, and that retry safety is included. The annotations cover the remaining safety-profile concerns.

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 schema fully documents the single `code` parameter, and the description adds meaningful provenance by saying it should come from a problem details body. The example `client_not_found` reinforces the expected format beyond the schema's own example.

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 exactly what the tool returns: one error code from the error catalog, including its HTTP status, meaning, remediation guidance, and retry safety. This clearly distinguishes it from sibling documentation and operation/webhook lookup tools.

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?

Tells the agent where to obtain the required `code` value, namely from a problem details body, and supplies an example such as `client_not_found`. It does not explicitly name alternatives or when-not-to-use cases, but the usage context is clear.

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

All Christian Background Checks Partner API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?