Skip to main content
Glama
cloudsmithy

Easysearch MCP Server

by cloudsmithy

ilm_policy_create

Create Index Lifecycle Management policies to automatically manage data through hot, warm, cold, and delete phases based on age and size thresholds.

Instructions

    创建 ILM 策略
    
    参数:
        policy_id: 策略 ID
        hot: 热阶段配置
        warm: 温阶段配置
        cold: 冷阶段配置
        delete: 删除阶段配置
        description: 策略描述
    
    示例 - 基本策略:
        ilm_policy_create("logs-policy",
            hot={
                "min_age": "0ms",
                "actions": {
                    "rollover": {"max_size": "50gb", "max_age": "30d"}
                }
            },
            delete={
                "min_age": "90d",
                "actions": {"delete": {}}
            }
        )
    
    示例 - 完整生命周期:
        ilm_policy_create("full-lifecycle",
            hot={
                "min_age": "0ms",
                "actions": {
                    "rollover": {"max_size": "50gb", "max_age": "7d"},
                    "set_priority": {"priority": 100}
                }
            },
            warm={
                "min_age": "30d",
                "actions": {
                    "shrink": {"number_of_shards": 1},
                    "forcemerge": {"max_num_segments": 1},
                    "set_priority": {"priority": 50}
                }
            },
            cold={
                "min_age": "60d",
                "actions": {
                    "set_priority": {"priority": 0}
                }
            },
            delete={
                "min_age": "90d",
                "actions": {"delete": {}}
            }
        )
    
    常用 actions:
        - rollover: 滚动索引 (max_size, max_age, max_docs)
        - shrink: 收缩分片数
        - forcemerge: 合并段
        - set_priority: 设置恢复优先级
        - allocate: 分配到特定节点
        - readonly: 设为只读
        - delete: 删除索引
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
policy_idYes
hotNo
warmNo
coldNo
deleteNo
descriptionNo
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates this is a creation operation (mutating) and provides extensive examples showing the structure of policy configurations. However, it doesn't mention important behavioral aspects like permissions required, whether policies are immediately active, error conditions, or what happens if a policy with the same ID already exists.

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

Conciseness3/5

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

The description is well-structured with clear sections for parameters, examples, and common actions. However, it's quite lengthy due to the detailed examples. While the examples are helpful, they dominate the description and could potentially be streamlined. The core purpose statement is clear but buried among the examples.

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?

For a complex tool with 6 parameters (including nested objects), 0% schema coverage, no annotations, and no output schema, the description does an excellent job explaining the tool's functionality. The examples provide concrete usage patterns, and the common actions section helps users understand what can be configured. The main gaps are the lack of behavioral context (permissions, error handling) and no output information.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by listing all 6 parameters with their Chinese names and providing two comprehensive examples showing exactly how to structure the hot, warm, cold, and delete phase configurations. The '常用 actions' (common actions) section further explains the semantic meaning of various actions that can be used within the phase configurations, adding significant value beyond the bare 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 clearly states '创建 ILM 策略' (Create ILM policy) which specifies the verb (create) and resource (ILM policy). It distinguishes this from sibling tools like ilm_policy_delete, ilm_policy_get, ilm_add_policy, and ilm_remove_policy by focusing on creation. However, it doesn't explicitly differentiate from slm_policy_create (snapshot lifecycle management) which might be conceptually similar.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when this should be used instead of ilm_add_policy (which applies an existing policy), or how it relates to other ILM operations. The examples show usage patterns but don't provide contextual guidance.

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/cloudsmithy/easysearch-mcp-server'

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