Skip to main content
Glama

Feeling Search — Art Style Reference & Prompt Encyclopedia

把一句描述解析成词与风格

word_analyze
Read-only

把一句中文/英文口语描述解析成感受词与视觉风格。默认纯本地词典(免费、不联网);本地一个词都没命中且允许时,才上云。返回 score 是相对值不是概率,styles[].matched 是可以直接引用给用户看的命中词。

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": {
      "text": "<text>"
    },
    "name": "word_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo用哪个语义引擎:auto 按是否含汉字判定。中文问句请用中文整句,英文问句请用英文整句,中英混写会落到中文引擎auto
textYes要解析的描述,最长 500 字
quotaNo已购额度令牌(响应头 X-FS-Quota 的值)。本机也可用环境变量 FS_QUOTA;远端 MCP 客户端没法设环境变量,就用这个参数
wordsNo返回几个感受词
stylesNo返回几个视觉风格
allow_cloudNo本地零命中且本机没装引擎时,是否允许上云(远端默认关闭;显式传 true 才会消耗额度)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / allow_cloud / description
      Previous value: -"本地零命中时是否允许上云(远端默认关闭;显式传 true 才会消耗额度)"New value: +"本地零命中且本机没装引擎时,是否允许上云(远端默认关闭;显式传 true 才会消耗额度)"
    • addedInput schema / properties / lang
      Added value: +{
      +  "default": "auto",
      +  "description": "用哪个语义引擎:auto 按是否含汉字判定。中文问句请用中文整句,英文问句请用英文整句,中英混写会落到中文引擎",
      +  "enum": [
      +    "auto",
      +    "zh",
      +    "en"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / quota
      Added value: +{
      +  "description": "已购额度令牌(响应头 X-FS-Quota 的值)。本机也可用环境变量 FS_QUOTA;远端 MCP 客户端没法设环境变量,就用这个参数",
      +  "maxLength": 256,
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds material context beyond them — the local-first/no-network default, the quota-consuming cloud fallback, and the caveat that score is a relative value rather than a probability. It does not describe latency or what happens on total miss with cloud disallowed, which is the one remaining behavioral gap.

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?

Three tight sentences: what it does, the local-vs-cloud policy, then the output caveats. Front-loaded and free of filler, though the return-value sentence could be slightly more structured given there are two distinct output fields.

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

Completeness5/5

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

No output schema exists, so the description carries the return-value burden and does so: it explains score's relative nature and the user-quotable styles[].matched field. Combined with 100% schema coverage on the six parameters and annotations covering the read-only profile, an agent has what it needs to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents lang, text, quota, words, styles, and allow_cloud thoroughly. The description only indirectly touches allow_cloud ('允许时') and adds nothing about word/style count semantics, so it sits at the baseline for a fully documented schema.

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?

The description states a specific verb+resource pair: parse a Chinese/English colloquial sentence into feeling words and visual styles, and it also names the two outputs (score, styles[].matched). It is clearly distinguishable from word_lookup/word_list/style_get in practice, but it never names a sibling or draws the boundary explicitly.

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?

It gives a clear default path (pure local dictionary, free, offline) and the condition for escalation to cloud (zero local hits AND allow_cloud). That is real usage guidance for the cloud branch, but there is no guidance on when to pick this tool over word_lookup, word_list, or style_get, which is what an agent actually needs to route.

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.