Skip to main content
Glama

China With Me — Hardware Prototyping & Exhibition MCP

book_consultation_or_quote

Submit a direct project inquiry or RFQ to JING (Stephanie) at China With Me (reply via Email or WhatsApp). Triggers an instant notification to the team in Shenzhen & Singapore.

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": {
      "name": "<name>",
      "email": "<email>",
      "service": "<service>",
      "message": "<message>"
    },
    "name": "book_consultation_or_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesClient name
emailYesClient email
phoneNoClient phone or WhatsApp number
messageYesProject details, timeline, product specs, or questions
serviceYesPrimary B2B service needed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: submission triggers an 'instant notification to the team in Shenzhen & Singapore' and replies arrive via Email or WhatsApp, telling the agent this dispatches to real humans and opens an asynchronous conversation. It omits whether duplicate submissions create duplicate tickets or what confirmation is returned, which keeps it out of 5 territory.

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?

Two sentences, front-loaded with the action and recipient, with the parenthetical and the notification sentence each carrying distinct information. No boilerplate or repetition of the schema. Slightly dense/telegraphic phrasing in the parenthetical costs it a point but nothing is wasted.

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

Completeness3/5

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

With five parameters, four required, no output schema, and open-world side effects, the description covers who receives the inquiry and how they respond, which is the most important behavior for a write operation. However, with no output schema present the description must explain what a successful call returns or confirms, and it says nothing about response shape, latency, or error conditions such as an invalid service value. That leaves a real gap for a mutation tool.

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%, with every property documented and the service enum listed, so the schema already carries parameter meaning. The description adds context for the 'message' field by implication ('Project details, timeline, product specs, or questions') but offers no additional syntax, format, or required-content guidance (e.g., what makes a message actionable for the Shenzhen team). Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb and artifact: submitting a 'direct project inquiry or RFQ' to a named human (JING/Stephanie) at a named organization. That is far more specific than the tool name alone and clearly identifies this as an outreach/lead-submission action. It stops short of a 5 because it never differentiates itself from overlapping siblings such as scope_hardware_prototyping_china or request_remote_exhibition_viewer, which an agent could plausibly confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of alternatives, despite several siblings covering adjacent intents (pricing lookup, prototyping scoping, exhibition viewer requests). An agent must infer from the words 'project inquiry or RFQ' alone that this is the tool for contacting the vendor directly rather than for getting information. The parenthetical about reply channel does not function as usage routing.

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.