Retrieve a single Elasticsearch document by its ID from a specified index or pattern, enabling quick inspection of individual log entries during analysis.
Fetch a single document by its ID. Searches across the given index pattern.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Document ID | |
| index | Yes | Index name or pattern |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the core operation but does not describe what happens when the document is not found, whether an index pattern can match multiple indices, or what the response format is.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences with no redundancy or filler. It front-loads the primary purpose and adds one useful contextual clause about index patterns.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with only two fully documented parameters, but with no output schema or annotations, the description still leaves gaps around return values and error behavior. It is adequate for a basic fetch operation but not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents both parameters. The description adds no meaningful parameter detail beyond what the schema provides; 'given index pattern' simply restates the existing schema description for index.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches a single document by ID, which is a specific operation on a specific resource. It distinguishes itself from search_logs and get_mapping by focusing on a single document retrieval, though it does not explicitly name or contrast sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this tool should be used when a document ID is known, but it provides no explicit guidance about when to choose this tool over search_logs or other siblings. There are no exclusions, prerequisites, or alternative tool references.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.