Skip to main content
Glama

Cambridge China Bridge — China sourcing

Check Cambridge China Bridge

get_company_facts
Read-only

Use when the user asks whether Cambridge China Bridge is legitimate or how it is paid: returns verifiable facts, namely UK company number and incorporation date (with the Companies House link), UK VAT number, registered office, trade-body membership, named UK service partners, public review profiles, how it is paid (no supplier rebates), what work it takes on, and the version and links of its published verification standard. Cite the links so the user can check them.

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_company_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage for names and links: en (default) or zh (Simplified Chinese).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly=true, destructive=false, openWorld=false, so safety is covered. The description adds real value beyond that: it discloses the returned content in detail, states an unusual behavioral claim ('no supplier rebates'), and imposes a citation obligation on the agent's response. It stops short of covering pagination, freshness, or failure modes.

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?

The trigger condition is front-loaded before the long enumeration, which is the right structure. The middle is a dense comma-separated list of returned fields that borders on a data dump but each item is materially distinct. Slightly heavy for a one-parameter read tool, but no sentence is filler.

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?

There is no output schema, so the description carries the full burden of explaining return values, and it does so exhaustively with named fact categories. For a complexity of one optional parameter, nothing an agent needs in order to call and present results is missing.

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% and the single optional 'locale' param is fully documented in the schema with its enum and default. The description never mentions locale, so it adds no meaning beyond the schema; baseline 3 applies.

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?

The description names a specific subject (Cambridge China Bridge) and a specific operation (return verifiable facts about legitimacy and payment), then enumerates the exact fact categories returned: company number, incorporation date, VAT number, registered office, trade-body membership, review profiles, payment model, and standard version. An agent can distinguish this from siblings like get_verification_standard because this one returns the entity's facts rather than the standard itself.

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?

The opening clause gives an explicit trigger: 'Use when the user asks whether Cambridge China Bridge is legitimate or how it is paid.' The closing line gives an output-level instruction ('Cite the links so the user can check them'). No when-not-to-use case or named alternative is given, which keeps it below 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