Skip to main content
Glama

TrustCheck by RecoupIQ: UK Company Facts

Request an evaluation API key

request_corporate_eval

Public onboarding tool (no API key required). Emails a 25-call live UK evaluation API key to a corporate work address (not a personal webmail address) and returns a payment link for a paid plan.

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": {
      "companyName": "<companyName>",
      "workEmail": "<workEmail>"
    },
    "name": "request_corporate_eval"
  }
}

Input Schema

NameRequiredDescriptionDefault
workEmailYesCorporate work email address (personal webmail domains are rejected).
companyNameYesLegal or trading name of your organisation.
intendedUseNoOptional summary of intended integration or data use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: it requires no API key, triggers an outbound email, issues a quota-limited 25-call UK key, and returns a payment link. It does not explain what happens on repeated invocations (annotations flag idempotentHint=false but the description is silent on whether a second call issues a second key) nor any rate limit.

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 sentences, front-loaded with the most important fact (no API key required) and then the outcome. Nothing is wasted and nothing is buried.

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?

For a three-parameter, no-output-schema onboarding call, the definition covers authentication status, side effect (email), quota, and the return artifact. The remaining gap is repeat-call behavior for a tool explicitly marked non-idempotent.

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 coverage is 100%, so the schema already documents all three parameters, including the webmail rejection rule that the description repeats. The description adds no syntax, format, or example detail and never mentions the optional intendedUse parameter, so this is baseline territory.

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+resource (requests an evaluation API key) and spells out both effects: it emails a 25-call live UK evaluation key and returns a payment link. This is clearly distinguishable from the sibling tools, which all resolve or assess existing company data rather than onboard a new user.

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?

Gives the key usage condition up front ('Public onboarding tool (no API key required)') and an eligibility constraint (must be a corporate work address, webmail rejected). No competing sibling is named, but none of the listed siblings plausibly overlaps with onboarding, so exclusions aren't needed.

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