Skip to main content
Glama
TKMD

ReftrixMCP

by TKMD
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

background.search

Read-onlyIdempotent

Search background design patterns with natural language. Filter by design type, industry, audience, or web page to find gradients, glassmorphism, SVG backgrounds, and more.

Instructions

BackgroundDesignをセマンティック検索します。グラデーション、グラスモーフィズム、SVG背景等の背景デザインパターンを自然言語で検索できます。designType（14種類）やwebPageIdでフィルタリング可能です。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo取得件数（1-50、デフォルト: 10）
queryYes検索クエリ（自然言語、1-500文字）
offsetNoオフセット（0以上、デフォルト: 0）
filtersNo検索フィルター
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. Changed4 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 / webPageUrl
      Added value: +{
+  "description": "WebページURLでフィルター / Filter by web page URL",
+  "format": "uri",
+  "type": "string"
+}
  2. Addedv0.1.8

TDQS

A4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=true and idempotentHint=true, which the description does not contradict. The description adds context about semantic search and filter capabilities, reinforcing the non-destructive, read-only nature. No behavioral traits are missing.

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?

The description is two concise sentences, front-loading the core purpose. Every sentence adds value: first states the action, second explains filtering capability. No unnecessary words.

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 full schema coverage and annotations, the description completes the picture for a search tool. It lacks mention of result format or pagination, but these are typical for search and can be inferred from the schema's limit/offset parameters.

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?

Input schema has 100% description coverage, so each parameter is already well-documented. The description only mentions query and two filter fields, adding minimal extra meaning. Baseline of 3 is appropriate.

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 clearly states it performs semantic search for background designs, specifying types like gradients, glassmorphism, and SVG backgrounds. It distinguishes from siblings such as design.search_by_image and layout.search by focusing on background design patterns.

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 description implies usage for natural language search of background designs and mentions filtering, but does not explicitly state when to use this tool versus alternatives like design.search_by_image or search.facets. No exclusion criteria or comparisons are provided.

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