Skip to main content
Glama
byeori-mcp

byeori-mcp

Official
by itworxlabs

search_byeori

Search monthly export and import trend reports by item and country to retrieve trade performance and growth rates.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden and does not meet it. It implies a read-only lookup but never confirms read semantics, and says nothing about permissions, rate limits, result size, or whether 'limit' truncates silently. Only the aggregation granularity (monthly, per item, per country) is added beyond the name.

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?

Two short fragments, zero filler, and the subject is front-loaded. But the terseness comes at the cost of substance: the second sentence is a data-scope label rather than an explanation of what the tool does with the query.

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?

An output schema exists, so return-value shape need not be described. Everything else is missing for a search tool with a required free-form query: what the query matches, what a query value should look like, and how many results come back by default are all left undocumented.

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 must explain both parameters and does not. The required 'query' is never defined — it could be an item name, a country, a HS/BEC code, or free text — and 'limit' is unmentioned, leaving its default and truncation behavior opaque.

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 dimensions available (품목별 · 국가별 수출입 실적과 증감률), so an agent can tell roughly what data is behind the tool. However, it never states the action — whether it searches, lists, or aggregates — and 'search_byeori' alone doesn't resolve that. It stops at describing the dataset rather than the operation on it.

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 guidance on when to call this versus anything else, no prerequisites, and no note on what a query should contain. With no sibling tools listed, there is no alternative to route to, but the agent still receives zero usage context.

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