Skip to main content
Glama
fastmcp-me

Agent Knowledge MCP

by fastmcp-me

create_index_metadata

Create metadata documentation for Elasticsearch indices to define purpose, data types, retention policy, and relationships, supporting index governance and clear usage context.

Instructions

Create metadata documentation for an Elasticsearch index to ensure proper governance and documentation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
index_nameYesName of the index to document
descriptionYesDetailed description of the index purpose and content
purposeYesPrimary purpose and use case for this index
data_typesNoTypes of data stored in this index (e.g., 'documents', 'logs', 'metrics')
usage_patternNoHow the index is accessed (e.g., 'read-heavy', 'write-heavy', 'mixed')mixed
retention_policyNoData retention policy and lifecycle managementNo specific policy
related_indicesNoNames of related or dependent indices
tagsNoTags for categorizing and organizing indices
created_byNoTeam or person responsible for this indexUnknown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description must convey behavioral traits. It only says 'create metadata', implying a write operation, but fails to disclose if it overwrites existing metadata, requires index existence, or has any side effects.

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?

Single sentence, no unnecessary words. Front-loaded with clear action and purpose.

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

Completeness2/5

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

Despite having an output schema (not shown), the description lacks explanation of return values. Also omits behavioral context for a tool with 9 parameters and 3 required fields, leaving gaps for an agent.

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 coverage is 100% with all parameters described. The description adds no extra insight into parameter interactions or constraints beyond the schema, so baseline 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 explicitly states 'Create metadata documentation for an Elasticsearch index', using a specific verb and resource. It clearly distinguishes from sibling tools like update_index_metadata and delete_index_metadata.

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 versus alternatives. Does not mention prerequisites (e.g., index must exist) or scenarios where update or delete would be preferred.

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/fastmcp-me/agentknowledgemcp'

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