Skip to main content
Glama

FarmTempo

mkt_search_rfqs

Read-onlyIdempotent

OPEN RFQ 목록. farm_id 지정 시 그 농가 조건 적합(품목×권역) = 입찰함(폴링).

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

Input Schema

NameRequiredDescriptionDefault
itemNo
regionNo
farm_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: with farm_id the result set changes to a condition-matched ('bid box') view, and the '(폴링)' note hints results are meant to be re-polled. That added context is real but written so cryptically that its operational meaning is hard to extract.

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

Conciseness3/5

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

It is short and front-loads the resource ('OPEN RFQ 목록'), which is good. But the compression crosses into opacity: '= 입찰함(폴링)' is a fragment that forces the agent to guess at matching and polling semantics, so terseness here costs clarity rather than saving it.

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?

With three optional, fully undocumented parameters and no output schema, the description should explain filter combination and result shape. It covers only the farm_id special case and leaves item/region and the polling expectation unexplained, which is not enough for an agent to invoke it with confidence.

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?

Schema description coverage is 0%, so the description carries the full burden for three parameters. It only explains farm_id (activates farm-condition matching) and merely names the item and region dimensions via '품목×권역' without saying whether they are free-text filters, how they combine with each other, or how they interact with farm_id. Two of three parameters remain effectively undocumented.

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 names the resource and the action implicitly ("OPEN RFQ 목록" = list of open RFQs), which is enough to know it retrieves open RFQs. However it is telegraphic, and the second sentence ("farm_id 지정 시 그 농가 조건 적합(품목×권역) = 입찰함") muddies purpose by introducing a matching/bid-box concept without explaining what that means. Nothing distinguishes it from siblings like mkt_search_listings beyond the resource name.

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?

The only usage signal is that supplying farm_id triggers farm-condition matching (item × region) and is described as a 'bid box' with polling. There is no statement of when to call this versus mkt_search_listings or mkt_create_rfq_draft, no prerequisites, and no note on when to omit filters versus pass them.

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