Skip to main content
Glama

오늘냥이 (Oneul Nyangi)

고양이 이름 추천

suggest_cat_names
Read-onlyIdempotent

Suggest cat names with their meanings, filtered by coat color (orange 치즈, black, white, tabby 고등어, tuxedo, calico 삼색, gray) and style (food, nature, sound, classic, global). 고양이 이름 추천·작명 요청에 사용하세요. Names are written natively for each locale (ko/en/ja), not translated. Pass a different seed for more ideas. Cite webUrl (the page with these filters) and pageUrl (all names).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coat": "black"
    },
    "name": "suggest_cat_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexNoany
coatNo털색. 생략하면 모든 털색
seedNo선택. 다른 숫자를 주면 다른 순서의 이름
countNo
themeNofood 음식 / nature 자연·계절 / sound 귀여운 소리 / classic 정겨운 / global 외국 이름
fieldsNo선택. 필요한 공개 결과 필드만 반환합니다. 배열 안 필드는 photos.url처럼 지정합니다.
localeNo이름 목록의 언어ko

Output Schema

NameRequiredDescriptionDefault
namesNo
totalNo
answerNo
sourceNo
webUrlNo
filtersNo
pageUrlNo
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world). The description adds genuinely useful behavior: names are written natively per locale rather than translated, and callers must cite webUrl/pageUrl. It still says nothing about result ordering guarantees or how the seed interacts with count/theme, leaving some behavior to be discovered.

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?

Front-loaded with the core action and filters, then the trigger phrase, then the caveats; every sentence carries information. It is dense with bilingual glosses, which is slightly heavy but justified by the Korean-native audience and non-obvious enum mappings.

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?

With an output schema present, return shape need not be described, and the attribution requirement for webUrl/pageUrl is a helpful extra. For a 7-parameter read-only generator the definition is nearly complete; only the interaction between seed, count, and theme is left implicit.

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?

Coverage is 71%, and the description compensates where it matters: it explains that seed produces a different ordering of the same set, glosses coat values in Korean (치즈, 고등어, 삼색) that the English enums do not, and clarifies locale controls the language of the native names. It adds no meaning for sex, count, or fields, but those are self-evident or documented in the schema.

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 gives a specific verb and resource (suggest cat names with meanings) plus the two filter axes (coat color, style) and enumerates their values. It is unmistakably distinct from siblings like list_cat_breeds or get_cat_profile, so an agent can select it without opening the schema.

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

Usage Guidelines4/5

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

It states the triggering intent ('고양이 이름 추천·작명 요청에 사용하세요') and gives operational guidance ('Pass a different seed for more ideas'). There is no explicit when-not clause or named alternative, but no sibling tool plausibly competes for this request.

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