Skip to main content
Glama
scrapedatshi

scrapedatshi-mcp

Official
by scrapedatshi

ingest_file

Upload a local file, chunk it, generate embeddings, and store the vectors in your vector database.

Instructions

Full RAG pipeline for local files: upload a file, embed the chunks using your embedding provider, and inject the vectors into your vector database.

Supported file formats: .pdf, .md, .txt, .yaml, .yml, .json Maximum file size: 50 MB

Use this when the user wants to ADD a local document (PDF, markdown, etc.) to their vector DB. This is the file-based equivalent of sync_to_vectordb.

Provide the ABSOLUTE path to the file on the user's local machine.

PRE-FLIGHT REQUIRED — before calling:

  1. Call verify_provider_key(embedding_provider, 'embedding') → get live embedding model list

  2. Present models to user, ask them to choose one

  3. Call list_vector_db_providers if user is unsure what config fields are needed

  4. Present Contextual Retrieval as a recommended upgrade: 'Would you like Contextual Retrieval (RAG 2.0)? It enriches each chunk with LLM-generated context before embedding, improving retrieval accuracy by 35–50%. Costs ~$0.001/chunk extra.'

  5. If contextual_retrieval=yes: call verify_provider_key(llm_provider, 'llm') too

Keys can be omitted if set as environment variables.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
overlapNoToken overlap between consecutive chunks. Default: 50.
file_pathYesAbsolute path to the local file to ingest. Supported: .pdf, .md, .txt, .yaml, .yml, .json. Example: 'C:/Users/user/Documents/report.pdf'
llm_modelNoLLM model name from verify_provider_key. Do not guess or hardcode.
vector_dbYesVector DB provider. Call list_vector_db_providers to see required config fields for each.
chunk_sizeNoTarget token count per chunk. Default: 512.
llm_api_keyNoAPI key for the LLM provider. Can be omitted if set as env var.
llm_providerNoLLM provider for contextual retrieval. Verify with verify_provider_key(provider, 'llm') first.
embedding_modelNoEmbedding model name from verify_provider_key. Do not guess or hardcode.
vector_db_configYesProvider-specific config. Call list_vector_db_providers for required fields. API keys within this config can be omitted if set as env vars.
embedding_api_keyNoAPI key for the embedding provider. Can be omitted if set as env var.
embedding_endpointNoPublic HTTPS endpoint for Ollama only (e.g. from ngrok). Not needed for cloud providers.
embedding_providerYesEmbedding provider. Call verify_provider_key(provider, 'embedding') first to get available models.
contextual_retrievalNoEnable RAG 2.0 contextual enrichment before embedding. Present as a recommended upgrade. Requires llm_provider and llm_model.
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses the full pipeline (upload, embed, inject), supported formats, max file size, and cost considerations for contextual retrieval. However, it does not explicitly state destructive behavior (e.g., whether existing vectors are overwritten or appended), nor does it mention rate limits or failure handling. While good, it leaves some behavioral gaps.

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 relatively long but well-structured. It front-loads the purpose and then provides structured bullet points for pre-flight steps and notes. Every section serves a purpose (supported formats, pre-flight, env var fallback), and the information density is high. A slight reduction in verbosity would not harm, but the current structure aids readability.

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 (13 parameters, 4 required, nested objects, no output schema), the description is quite complete. It covers pre-flight workflow, file format/size limits, cost notes, sibling equivalence, and env var handling. It does not describe the return value or error scenarios, but since no output schema exists, the description could have briefly mentioned what the agent should expect (e.g., success confirmation). Overall, it's satisfactory for a complex tool.

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 coverage is 100%, so the baseline is 3. The description adds significant meaning beyond the schema by explaining pre-flight dependencies (e.g., 'embedding_model' must come from verify_provider_key, 'vector_db_config' requires list_vector_db_providers), the role of 'contextual_retrieval' as a recommended upgrade, and the absolute path requirement for 'file_path'. This contextual workflow information is not present in the schema alone.

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: a full RAG pipeline for local files (upload, embed, inject into vector DB). It specifies the use case (adding a local document to vector DB) and explicitly distinguishes from the sibling 'sync_to_vectordb' by calling itself the file-based equivalent. The verb 'ingest' combined with the detailed pipeline leaves no ambiguity.

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 provides extensive usage guidelines, including detailed pre-flight steps (verify_provider_key, list_vector_db_providers, present contextual retrieval upgrade). It states when to use the tool (when user wants to ADD a local document), notes that API keys can be omitted if set as environment variables, and gives file path instructions. The conditional logic for contextual_retrieval is also explained.

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/scrapedatshi/scrapedatshi-mcp'

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