Skip to main content
Glama
Sign In
kr-pc-deals-mcp

kr-pc-deals-mcp

by edward-kim-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

compare_prices

Compare prices for identical PC parts across Danawa and Compuzone. Enter a product keyword and category to see which retailer offers the lower price.

Instructions

동일 제품의 다나와/컴퓨존 간 가격을 비교합니다.

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": {
      "query": "<query>"
    },
    "name": "compare_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes검색 키워드
categoryNo부품 카테고리

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.7

TDQS

B3.3/5.0
Behavior2/5

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

There are no annotations and no output schema, so the description carries the full burden of explaining behavior. It only says 'compares', without stating what the returned data looks like, whether it fetches live prices, or how it handles cases where the same product is not available on both sites.

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?

The description is a single, front-loaded sentence with no wasted words. It is concise and readable, but it is so brief that it omits useful usage and output context.

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?

Given that there is no output schema and no annotations, the description is not complete enough for an agent to confidently call the tool. It lacks return-value expectations, failure behavior, and explicit guidance about when to choose this tool over related siblings.

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 100%, so the schema already documents query and category. The description adds meaningful nuance by emphasizing 'same product', which tells the agent the query should be a specific product identifier rather than a broad search term.

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?

The description uses a specific verb ('compares') and a precise resource ('prices between Danawa and Computzone for the same product'). It distinguishes the tool from siblings like get_price_history and find_lowest_price by explicitly scoping it to a two-retailer comparison.

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?

No guidance is provided for when to use this tool versus alternatives such as find_lowest_price or get_price_history. The description says what the tool does but not which situations call for it or when a sibling would be more appropriate.

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

Deploy Server

Other Tools