FlexOrch MCP

Search Documents

dataset.search

Read-onlyIdempotent

Search across all indexed FlexOrch datasets by keyword or meaning.

Use this to find specific documents or records without processing a new file.
Requires at least one dataset to exist. Structured search works on all plans.
Semantic and hybrid modes require a Pro plan — a clear upgrade message is returned
if the plan is insufficient. mode='auto' picks structured on free plans, hybrid on Pro+.

Args:
    query: Search query — natural language or keyword. Max 1000 characters.
    top_k: Number of results to return. Default: 5, max: 50.
    mode: Search strategy — auto (default), structured, semantic, hybrid.
          semantic and hybrid require Pro plan.
    document_type: Filter to a specific document type, e.g. invoice (optional).
    language: Filter by document language, ISO 639-1 code, e.g. en, de, tr (optional).
    quality_grade: Filter by quality grade: A, B, C, or D (optional).

Input Schema

TableJSON Schema

Name	Required	Default
`mode`	No	auto
`query`	Yes
`top_k`	No
`language`	No
`document_type`	No
`quality_grade`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No
`error`	No
`query`	No
`isError`	No
`results`	No
`total_results`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 3, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description adds meaningful behavioral detail beyond the readOnly/idempotent annotations: it explains plan-gated modes, the upgrade message, the auto-mode resolution logic between free and Pro plans, and the dataset existence requirement. These are non-obvious behaviors an agent needs to know before invoking.

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?

The description is well-structured: a clear one-sentence purpose, followed by usage context and plan behavior, then a compact Args list. Every sentence contributes necessary operational detail, and the most important behavioral nuances are front-loaded before the parameter details.

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?

The tool has six parameters, plan-dependent behavior, and a required precondition; the description covers all of these, including the error/upgrade path. The presence of an output schema means return-value documentation is not required here, and nothing essential to correctly calling the tool is missing.

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?

Schema description coverage is 0%, but the Args block fully compensates by explaining every parameter: query length limit, top_k default and max, mode options with plan requirements, document_type example, language format with ISO 639-1 examples, and quality_grade allowed values. This is far more informative than the raw 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 opens with a specific verb and resource: 'Search across all indexed FlexOrch datasets by keyword or meaning.' It clearly distinguishes itself from siblings by emphasizing search over already-indexed data and explicitly contrasting with 'without processing a new file.'

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

Usage Guidelines4/5

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

It states when to use the tool: 'Use this to find specific documents or records without processing a new file.' It also provides a precondition ('Requires at least one dataset to exist') and plan-based guidance for mode selection. However, it does not explicitly name alternative sibling tools or state when not to use it beyond the 'without processing' implication.

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

All FlexOrch MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?