Subindex MCP Server

start_table_validation

Validate an uploaded table by checking for matching prior configurations or using provided instructions. Optionally bypass the interview with a config ID or natural-language description.

Instructions

Confirm the upload and detect matching prior configs.

Call this immediately after upload_file completes (or after the curl upload finishes when using HTTP/Railway transport). Returns config_matches with match_score — if score >= 0.85 a prior config can be reused directly.

instructions: Optional natural-language description of what to validate and how (e.g. "This table lists clinical trials — validate that trial IDs, phase, and primary endpoints are accurate"). When provided, the upload interview is bypassed: the AI reads the table structure + instructions and generates a config directly without asking clarifying questions. Preview is auto-triggered immediately after.

config_id: Optional ID of a known prior configuration to reuse directly. When provided, skips matching and the interview entirely — applies the config and queues the preview immediately. Response includes preview_queued=true and job_id. Use when you already know the config_id (e.g. from a previous job's get_results response).

Config generation and the 3-row preview are free. Full validation is charged at approve_validation — you still see the cost at preview_complete before anything is billed. If balance is insufficient at that point, approve_validation returns an insufficient_balance error.

Input Schema

TableJSON Schema

Name	Required	Description
`session_id`	Yes	Session ID returned by upload_file.
`s3_key`	Yes	S3 key returned by upload_file identifying the uploaded file.
`filename`	Yes	Original filename of the uploaded file.
`instructions`	No	Optional natural-language description of what to validate; bypasses the upload interview when provided.
`config_id`	No	Optional ID of a prior configuration to reuse; skips the interview and queues the preview immediately.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Tool Definition Quality

A4.5/5.0

Behavior4/5

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

Annotations indicate the tool is not read-only and not destructive. The description adds behavioral context: config generation and preview are free, full validation is charged at approve_validation, and balance insufficiency leads to an error. It does not fully describe all side effects, but adds value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear separation of concepts and front-loaded key information. It is slightly verbose but every sentence adds value. Could be more concise, but efficiently conveys important details.

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?

Given the tool's complexity (5 parameters, output schema exists), the description covers the workflow, charging model, and error handling. It does not detail return values, but output schema likely provides that. It is adequately complete.

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?

The input schema already provides 100% coverage with descriptions, but the description elaborates on parameters like instructions and config_id, explaining their effects (bypassing interview, skipping matching). This adds meaningful context beyond 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 clearly states the tool's purpose: to confirm upload and detect matching prior configs. It specifies the action verb ('confirm', 'detect'), the resource (upload and prior configs), and distinguishes from siblings like start_reference_check or start_table_maker.

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?

The description explicitly instructs to call this immediately after upload_file completes, and explains when to use config_id vs instructions. It also mentions that if match_score >= 0.85, a prior config can be reused directly, providing clear usage context.

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

Install Server

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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/EliyahuAI/mcp-server-subindex'

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