Skip to main content
Glama

seme_lookup

Looks up HowNet sememes for a Chinese word via OpenHowNet to provide fine-grained, interpretable lexical semantics for entity typing and sememe-based similarity.

Instructions

HowNet sememe (义原) lookup for a Chinese word via OpenHowNet. Fine-grained interpretable lexical semantics - useful for entity typing and sememe-based similarity.

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": {
      "word": "<word>"
    },
    "name": "seme_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoauto
wordYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the backing service (OpenHowNet) and the Chinese-only scope, which is genuinely useful, but says nothing about network dependency, latency, or what happens when a word has no sememes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core action front-loaded and the downstream use case trailing. No filler or restatement of the tool name.

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

Completeness3/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 values need no explanation, and the Chinese/OpenHowNet framing covers the essentials. However, the entirely undocumented 'lang' parameter and the absence of any failure-mode or dependency note leave real gaps for a two-parameter tool with zero schema coverage.

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 compensate and does not. The 'lang' parameter (default 'auto') is never mentioned or explained anywhere, and 'word' is only implicitly constrained to Chinese via the phrase 'for a Chinese word'.

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?

States a specific verb and resource: sememe lookup for a Chinese word, sourced from OpenHowNet. This is clearly distinct from the WordNet siblings in the tool list, though it does not name wordnet_lookup explicitly to draw the contrast.

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?

The clause 'useful for entity typing and sememe-based similarity' implies a usage context but gives no explicit when-to-use rule, no exclusions, and does not name wordnet_lookup or wordnet_similarity as the alternatives for English or similarity tasks.

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