Skip to main content
Glama
Sign In

Cambridge China Bridge — China sourcing

by uk.co.camchinabridge
OverviewDiscussionsAdmin

Send an enquiry to Cambridge China Bridge

submit_enquiry

Use only when the user has asked to contact Cambridge China Bridge or to get a quote: sends the user's sourcing enquiry or quote request to them by email, and they reply to the user directly. It sends only when user_confirmed is true, meaning the user has seen exactly what will be sent and agreed. All contact details are the user's own.

Input Schema

NameRequiredDescriptionDefault
nameYesThe user's name.
emailYesThe email address to reply to.
phoneNoThe user's phone number, if they want to give one.
companyNoThe user's company, if they gave one.
messageNoAnything else the user wants to say.
productYesWhat they want sourced: product, specification or link, quantity, target price.
assistantNoWhich assistant is sending this (chatgpt, claude, gemini, perplexity, copilot or other). Optional.
source_pageNoThe CCB page path the user was reading, if known. Path only, starting with /; no query or personal data.
user_confirmedYestrue only if the user has seen these details and agreed to send them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / source_page
      Added value: +{
+  "description": "The CCB page path the user was reading, if known. Path only, starting with /; no query or personal data.",
+  "maxLength": 200,
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive behavior. The description adds concrete context: it sends by email, CCB replies directly, sending is gated on user_confirmed, and contact details are the user's own. It does not discuss duplicate-submission or failure behavior, but the annotations cover much of the safety profile.

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?

Three compact sentences, front-loaded with the usage restriction, then the action, confirmation guard, and privacy note. Every sentence contributes useful information with no repetition.

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 nine-parameter action tool with full schema descriptions and annotations, the description covers trigger conditions, action, confirmation requirement, privacy handling, and reply path. No output schema exists, and the description gives enough context for correct invocation.

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 all nine parameters are already documented in the input schema. The description reinforces the meaning of user_confirmed and the privacy of contact details, but adds no field-level syntax or format guidance beyond the schema. Baseline 3 is appropriate.

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 action and resource: it sends the user's sourcing enquiry or quote request by email to Cambridge China Bridge, and CCB replies directly to the user. The 'use only when...' clause clearly separates this action tool from the read-only 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit exclusive trigger condition: use only when the user has asked to contact Cambridge China Bridge or to get a quote. It also states the required user_confirmed prerequisite, leaving little ambiguity about when to call it.

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

All Cambridge China Bridge — China sourcing toolsInspect
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