Skip to main content
Glama
arpe-io

arpeio-mcp

Official
by arpe-io

search_docs

Read-onlyIdempotent

Search Arpe.io documentation and blog to find answers about CLI parameters, use cases, parallelism strategies, integrations, and best practices.

Instructions

Search arpe.io documentation and blog for answers about CLI parameters, use cases, parallelism strategies, integrations, and best practices. Call this when unsure about a parameter value, need an example command, or want the recommended approach for a specific source/target/format combination. Searches across all product documentation (FastBCP, FastTransfer, LakeXpress, MigratorXpress) and the arpe.io blog simultaneously. Does not execute anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_kNoMaximum number of results to return (1-10).
questionYesSearch query — a question or keywords about arpe.io tools, parameters, or use cases (e.g., 'how to use Ntile parallelism', 'parquet compression options', 'Oracle to Snowflake pipeline').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results returned.
queryNoThe search query that was run.
statusYes'ok' when the call succeeded; 'error' when the parameters failed validation or execution failed.
resultsNoRanked documentation/blog chunks.
index_readyNoFalse while indexes are still loading.
fully_loadedNoFalse while some sources are still loading.
Behavior5/5

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

Adds that it searches across multiple product docs and blog simultaneously, does not execute anything, complementing annotations.

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?

Two concise sentences plus product list, front-loaded with purpose, no wasted words.

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

Completeness5/5

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

For a search tool with rich annotations and output schema, description covers scope, usage, and safety fully.

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 already covers both parameters (100% coverage). Description reinforces but adds no new parameter details beyond context.

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?

Clearly states it searches documentation and blog, distinguishes from execution/info siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to call: when unsure about parameter, need example, or want recommended approach.

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/arpe-io/arpeio-mcp'

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