Skip to main content
Glama

BeaconMFG – China Supplier Directory

answer_sourcing

续接 start_sourcing 的澄清轮次:把用户对澄清问题的回答写回,服务端据此重新检索(不是在旧结果里二次过滤 —— 过滤只能筛掉已有的,重检才能把更适合的捞上来)。 answers 的键用 clarifying_questions[].field(city / proc / cert),值为该问的 options[].value;此外可传 keyword 追加自由关键词。 回执里的 applied 是已被采纳的字段,ignored 是没被采纳的(多半是字段名写错)——看到 ignored 非空请对照 field 重发,不要以为已经生效。 轮次用完(2 轮)或问题已问清 → stage 变 shortlist,直接给初选名单。

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": {
      "session_id": "<session_id>"
    },
    "name": "answer_sourcing"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersNo澄清回答,如 {"city":"东莞","proc":"injection_molding"};可加 keyword 追加自由关键词
session_idYesstart_sourcing 返回的 session_id(必填)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full disclosure burden and does it well: it states the server re-retrieves rather than filters prior results, discloses the 2-round limit, and explains the applied/ignored receipt semantics plus the stage transition to shortlist. These are exactly the non-obvious behaviors an agent would otherwise get wrong.

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?

Every sentence earns its place: the continuation rule first, then the retrieval-vs-filter contrast, then the payload format, then the receipt contract, then the terminal state. The bold emphasis lands on the two facts most likely to cause an agent error.

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 must explain the return contract itself, and it does: applied vs ignored, the stage field, and the shortlist terminal state. Nothing an agent needs in order to call this correctly and interpret the response is missing.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: answers keys must be clarifying_questions[].field names (city/proc/cert), values must come from that question's options[].value, and keyword can be added for free text. It also explains what happens when a key is misspelled (it appears in ignored).

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 gives a specific verb+resource: writing the user's answers to clarification questions back into the session started by start_sourcing. It also contrasts the mechanism with filtering old results, which implicitly separates it from a refinement-style sibling, though it never names that sibling explicitly.

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?

Precise context is given: use it after start_sourcing's clarifying round, and it terminates when the 2-round budget is spent or the questions are resolved, at which point stage becomes shortlist. What is missing is an explicit statement of when to choose this over the named siblings (e.g. refine_sourcing) for the same session.

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.