Apache Iceberg MCP Server

Search Iceberg Java source

iceberg_source_search

Read-onlyIdempotent

Find exact literal matches within Apache Iceberg's production Java source code, using paginated results to locate specific strings.

Instructions

Perform a bounded literal (not regex) search across indexed production Java source files.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "literal": "<literal>"
    },
    "name": "iceberg_source_search"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`cursor`	No	Opaque cursor from the prior page.
`literal`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds that the search is bounded (limit applies), literal rather than regex, and scoped to indexed production Java files, giving useful operational context beyond what the annotations already provide.

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?

A single, tightly worded sentence that front-loads the verb and packs in the resource, scope, and search type. There is no redundancy or filler, making it easy for an agent to parse quickly.

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 simple read-only search tool with an output schema, the description covers what is searched, how it is searched (literal), and the bounded nature of results. It would benefit from explicit routing to sibling API search tools, but nothing essential for invoking the tool correctly is missing.

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

Parameters4/5

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

Only one of three schema properties (cursor) has a schema description, so the description must compensate for the other two. It does so by clarifying that 'literal' is a literal search string and that the search is 'bounded', which maps to the limit parameter; cursor is already documented in the schema.

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 names a specific action ('search'), a specific resource ('indexed production Java source files'), and a key constraint ('bounded literal (not regex)'). This clearly separates it from sibling iceberg_api_search (API docs) and iceberg_source_find_implementations (implementation discovery), making its purpose unmistakable.

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 conveys that the tool is for literal source-code search and explicitly notes it is not regex, implying a regex search would need a different tool. However, it does not name any sibling tool or state when to choose API search vs source search, leaving some routing guidance implicit rather than explicit.

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

Deploy Server