Skip to main content
Glama

FarmTempo

mkt_create_rfq_draft

Read-onlyIdempotent

AI RFQ 초안 — 예측 API로 밴드+근거+신뢰도 등급. 신뢰도 하위 등급이면 밴드 null+사유. sync def(스레드풀 실행) — 같은 :8003 워커로의 예측 자기호출이 이벤트 루프를 막지 않도록.

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": "mkt_create_rfq_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
bNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

With readOnlyHint=true and idempotentHint=true already declared, the description does add one genuinely useful behavioral fact: a low confidence grade yields a null band plus a reason. However, it never resolves the tension between the "create"/"draft" framing and readOnlyHint — it does not say whether anything is persisted or whether the call is purely a projection. The thread-pool/event-loop sentence describes internal implementation, not behavior an agent can act on.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but roughly half the text ("sync def(스레드풀 실행) — ... 이벤트 루프를 막지 않도록") is developer implementation detail irrelevant to tool selection. The mixed Korean/English phrasing and the internal port reference add noise rather than clarity. Trimming to the first two sentences would strengthen it considerably.

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

Completeness2/5

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

The tool takes an opaque nested object and has no output schema, so the description must carry the input contract and the return shape; it does neither beyond the confidence-null rule. Given a nested, untyped parameter and a non-obvious side-effect profile against readOnlyHint, this is materially under-specified for an agent to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter "b" is a free-form nested object with additionalProperties: true and zero schema description coverage, so the schema offers essentially nothing. The description never references it — no shape, no expected keys, no example — leaving the only input entirely opaque. It does not compensate for the coverage gap.

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

Purpose3/5

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

The description says it produces an "AI RFQ 초안" containing a predicted band, rationale, and confidence grade via a prediction API, which hints at the resource and output. But it never states a clear verb (create/generate) or scope, and the name's "create" framing is left implicit. An agent can guess the purpose but would not be certain what the tool actually returns or persists.

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 guidance, no prerequisites, and no mention of the related sibling mkt_search_rfqs. Nothing indicates when a draft should be generated versus searched for or reused. The only conditional statement ("low confidence → band null + reason") describes output behavior, not invocation guidance.

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