Skip to main content
Glama

RAG chunking plan

submit_rag_chunking_plan
Idempotent

Produce a chunking plan and retrieval config for a set of documents and query samples. Before indexing a corpus, to fix chunk size and retrieval settings. Do not choose this when you need retrieval quality measured, which needs embeddings. Example requests: Plan the chunking for this RAG corpus. | What chunk size should I use for these documents? | Give me a retrieval config for these documents.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_rag_chunking_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare it is not read-only, is idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds nothing about the priced-job workflow implied by quote_id/accepted_price, the fact that this is a job submission rather than an inline computation, or what the agent gets back. Consistent with annotations, but thin beyond them.

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?

Purpose and the exclusion are front-loaded and the example requests are genuinely useful for matching user phrasing. The sentence 'Before indexing a corpus, to fix chunk size and retrieval settings' is a dangling fragment that could be merged cleanly, and the three examples add length without new information.

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?

Output schema exists, so return values need no explanation, and the schema fully documents inputs and the quote/authorization fields. For a 4-parameter, non-destructive, idempotent tool, the description covers purpose, timing, and the key exclusion, leaving no agent-blocking gap.

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?

With 75% schema description coverage, the nested documents/queries fields and the quote/price fields are already documented in the schema. The description only restates that a 'set of documents and query samples' is needed, adding no format, size, or authorization guidance beyond what the schema carries.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and deliverable: 'Produce a chunking plan and retrieval config' from documents and query samples. It also separates the tool from a related class of work ('retrieval quality measured, which needs embeddings'), though it never names the sibling tool that does that measurement, so the differentiation is categorical rather than concrete.

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?

Usage timing is explicit ('Before indexing a corpus, to fix chunk size and retrieval settings') and there is an explicit exclusion ('Do not choose this when you need retrieval quality measured'). What is missing is a named alternative to route to in that excluded case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources