Skip to main content
Glama

검색 (ChatGPT 호환)

search
Read-onlyIdempotent

베이비뉴스 기사와 Q&A 를 한 번에 찾는다. 결과마다 id 와 원문 url 이 있다. 질문 예: "부모급여 신청 방법", "신생아 예방접종 일정". Searches BabyNews (Korean parenting news) articles and Q&A.

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

Input Schema

NameRequiredDescriptionDefault
queryYes찾을 말(자연어 가능)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that each result carries an id and the original source url, which is genuinely useful given there is no output schema, but it says nothing about result counts, ranking, or pagination limits.

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?

Very short and front-loaded: the purpose lands in the first clause, then result shape, then examples. The final English sentence largely restates the Korean opening, so there is mild redundancy, but it aids clarity for English-only agents and costs little.

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

Completeness4/5

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

For a one-parameter read-only search with full schema coverage and annotations, the description is close to sufficient: it states scope, gives example queries, and notes the id/url fields in results. Minor gaps remain around result volume and whether matches are ranked or capped, but nothing essential to correct invocation 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 100% and the single query parameter is already documented as accepting natural language, so the baseline is high. The description still adds value by supplying concrete example queries that calibrate what a good query looks like, going slightly beyond the schema text.

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?

"베이비뉴스 기사와 Q&A 를 한 번에 찾는다" gives a specific verb (find) plus the two resources covered, and "한 번에" signals this is the combined search rather than a single-domain one. It does not name siblings such as search_articles or search_qa, so the differentiation is implied rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Example queries ("부모급여 신청 방법", "신생아 예방접종 일정") imply the intended use case — natural-language parenting questions spanning news and Q&A — but there is no statement of when to prefer this over the domain-specific search tools, nor any exclusion or prerequisite.

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.