Skip to main content
Glama
TKMD

ReftrixMCP

by TKMD
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

narrative.search

Read-onlyIdempotent

Search design narratives and layouts using natural language queries or embeddings. Supports hybrid vector and full-text search with filters for tags, audience, industry, and more.

Instructions

世界観・レイアウト構成でセマンティック検索します。自然言語クエリ（例: "サイバーセキュリティ感のあるダークなデザイン"）または768次元Embeddingで検索可能。Hybrid Search（Vector + Full-text）でRRF統合。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo検索クエリ（queryまたはembeddingのいずれか必須）
filtersNo
optionsNo
embeddingNo直接Embedding指定（768次元、queryまたはembeddingのいずれか必須）
profile_idNo嗜好プロファイルID（検索結果のリランキングに使用） / Preference profile ID (used for search result reranking)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv0.3.0
    • addedInput schema / properties / filters / properties / audience
      Added value: +{
+  "description": "ターゲットオーディエンス（例: b2b, b2c, enterprise） / Target audience filter",
+  "maxLength": 100,
+  "type": "string"
+}
    • addedInput schema / properties / filters / properties / industry
      Added value: +{
+  "description": "業種フィルター（例: tech, finance, healthcare） / Industry filter",
+  "maxLength": 100,
+  "type": "string"
+}
    • addedInput schema / properties / filters / properties / tags
      Added value: +{
+  "description": "タグフィルター / Tag filter",
+  "items": {
+    "maxLength": 50,
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
    • addedInput schema / properties / filters / properties / webPageId
      Added value: +{
+  "description": "WebページIDでフィルター / Filter by web page ID",
+  "format": "uuid",
+  "type": "string"
+}
    • addedInput schema / properties / filters / properties / webPageUrl
      Added value: +{
+  "description": "WebページURLでフィルター / Filter by web page URL",
+  "format": "uri",
+  "type": "string"
+}
  2. Addedv0.1.8

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint and idempotentHint, so core safety is covered. Description adds value by explaining search modes (hybrid, RRF) but does not disclose return format or pagination behavior. No contradiction with annotations.

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?

Two concise sentences in Japanese, front-loading the purpose. No extraneous information, though could benefit from more structured detail.

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?

Given 5 parameters, no output schema, and moderate complexity (hybrid search, filters, reranking), the description provides a good overview but lacks details on filters, profile_id, result structure, and pagination. Adequate but not fully comprehensive.

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 has 60% description coverage (moderate), but the description does not add significant meaning beyond schema. It mentions query/embedding and hybrid search, but filters and options are not further explained. Baseline 3 given schema coverage.

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?

Description clearly states it performs semantic search on worldview/layout composition using natural language or embeddings, with hybrid search. Implicitly differentiates from siblings like layout.search or part.search by focusing on worldview, but does not explicitly name alternatives.

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?

No guidance on when to use this tool vs siblings (e.g., background.search, search.unified) or when to choose query vs embedding. Does not specify prerequisites or typical use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TKMD/ReftrixMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server