Skip to main content
Glama
lmwharton

lmwharton/sieve-mcp

sieve_dataroom_add

Add a document to a deal's data room, creating the deal if needed. Upload a pitch deck, financials, or other document via file, text, or URL for screening.

Instructions

Add a document to a deal's data room. Creates the deal if needed.

This is the primary way to get documents into Sieve for screening. Upload a pitch deck, financials, or any document -- then call sieve_screen to analyze everything in the data room.

Provide company_name to create a new deal (or find existing), or deal_id to add to an existing deal.

Provide exactly one content source: file_path (local file), text (raw text/markdown), or url (fetch from URL).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesDocument title (e.g. "Pitch Deck Q1 2026").
company_nameNoCompany name -- creates deal if new, finds existing if not.
deal_idNoAdd to an existing deal (from sieve_deals or previous sieve_dataroom_add).
website_urlNoCompany website URL (used when creating a new deal).
document_typeNoType: 'pitch_deck', 'financials', 'legal', or 'other'.other
file_pathNoPath to a local file (PDF, DOCX, XLSX). The tool reads and uploads it.
textNoRaw text or markdown content (alternative to file).
urlNoURL to fetch document from (alternative to file).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for sieve_dataroom_add. Decorated with @mcp.tool, accepts title, company_name, deal_id, website_url, document_type, file_path, text, url parameters. Delegates to client.dataroom_add().
    @mcp.tool(
        annotations={
            "readOnlyHint": False,
            "destructiveHint": False,
            "openWorldHint": True,
        }
    )
    async def sieve_dataroom_add(
        title: str,
        company_name: str = "",
        deal_id: str = "",
        website_url: str = "",
        document_type: str = "other",
        file_path: str = "",
        text: str = "",
        url: str = "",
    ) -> dict:
        """Add a document to a deal's data room. Creates the deal if needed.
    
        This is the primary way to get documents into Sieve for screening.
        Upload a pitch deck, financials, or any document -- then call sieve_screen
        to analyze everything in the data room.
    
        Provide company_name to create a new deal (or find existing),
        or deal_id to add to an existing deal.
    
        Provide exactly one content source: file_path (local file),
        text (raw text/markdown), or url (fetch from URL).
    
        Args:
            title: Document title (e.g. "Pitch Deck Q1 2026").
            company_name: Company name -- creates deal if new, finds existing if not.
            deal_id: Add to an existing deal (from sieve_deals or previous sieve_dataroom_add).
            website_url: Company website URL (used when creating a new deal).
            document_type: Type: 'pitch_deck', 'financials', 'legal', or 'other'.
            file_path: Path to a local file (PDF, DOCX, XLSX). The tool reads and uploads it.
            text: Raw text or markdown content (alternative to file).
            url: URL to fetch document from (alternative to file).
        """
        return await client.dataroom_add(
            company_name=company_name,
            deal_id=deal_id,
            website_url=website_url,
            title=title,
            document_type=document_type,
            file_path=file_path,
            text=text,
            url=url,
        )
  • Registration of sieve_dataroom_add as an MCP tool via the @mcp.tool decorator with annotations (destructiveHint=False, openWorldHint=True).
    @mcp.tool(
        annotations={
            "readOnlyHint": False,
            "destructiveHint": False,
            "openWorldHint": True,
        }
    )
  • Client-side helper function dataroom_add that builds the request body and sends it to POST /api/v1/public/dataroom. Handles file_path (base64 encoding), text, and url content sources.
    async def dataroom_add(
        company_name: str = "",
        deal_id: str = "",
        website_url: str = "",
        title: str = "Document",
        document_type: str = "other",
        file_path: str = "",
        text: str = "",
        url: str = "",
    ) -> dict[str, Any]:
        """Add a document to a deal's data room."""
        body: dict[str, Any] = {"title": title, "document_type": document_type}
        if company_name:
            body["company_name"] = company_name
        if deal_id:
            body["deal_id"] = deal_id
        if website_url:
            body["website_url"] = website_url
    
        if file_path:
            import base64
            import mimetypes
    
            file_name = os.path.basename(file_path)
            content_type = mimetypes.guess_type(file_path)[0] or "application/octet-stream"
    
            with open(file_path, "rb") as f:
                file_bytes = f.read()
    
            body["file_base64"] = base64.b64encode(file_bytes).decode("ascii")
            body["file_name"] = file_name
            body["file_content_type"] = content_type
        elif text:
            body["text"] = text
        elif url:
            body["url"] = url
    
        return await _request("POST", "/dataroom", json_body=body, timeout=60.0)
  • Python type annotations defining the input schema for sieve_dataroom_add: title (str, required), company_name (str, optional), deal_id (str, optional), website_url (str, optional), document_type (str, default 'other'), file_path (str, optional), text (str, optional), url (str, optional). Returns dict.
    async def sieve_dataroom_add(
        title: str,
        company_name: str = "",
        deal_id: str = "",
        website_url: str = "",
        document_type: str = "other",
        file_path: str = "",
        text: str = "",
        url: str = "",
    ) -> dict:
  • MCP server instructions referencing sieve_dataroom_add as the primary way to add documents to a deal's data room.
    instructions=(
        "Sieve is an AI-powered startup due diligence platform. "
        "It scores startups across 7 IMPACT-X dimensions (each 0-20, total 0-140) "
        "and returns a Take Meeting / Pass / Need More Info recommendation.\n\n"
        "WORKFLOW:\n"
        "1. Add documents: sieve_dataroom_add with company_name + file/text/url\n"
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, and is open-world. The description adds that it 'Creates the deal if needed,' which is a key behavioral trait, and also constrains content sources to exactly one. This goes beyond what annotations provide.

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 about six sentences, front-loading the core purpose, then providing usage context, then parameter guidance. Every sentence adds value without redundancy.

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?

Given 8 parameters, annotations, output schema presence, and sibling tools, the description covers the tool's purpose, side effects, parameter constraints, and integration with sieve_screen. It is sufficiently complete for an AI agent to use correctly.

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?

Schema coverage is 100% with good descriptions. The description adds semantics by explaining the interplay between company_name and deal_id, and explicitly states the exclusivity of file_path, text, and url. This adds value beyond the property descriptions.

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 adds a document to a deal's data room and can create the deal if needed. It uses specific verbs and resources ('Add a document', 'creates the deal') and distinguishes from siblings like sieve_screen which analyzes, and sieve_deals which lists deals.

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?

The description says 'This is the primary way to get documents into Sieve for screening' and 'then call sieve_screen to analyze everything in the data room,' providing clear context for when to use this tool and a follow-up action. It doesn't explicitly list exclusions, but the guidance is strong.

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/lmwharton/sieve-mcp'

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