Skip to main content
Glama
lmwharton

lmwharton/sieve-mcp

sieve_results

Read-only

Retrieve Sieve analysis results: score, meeting decision, executive summary, strengths, and concerns for a completed deal by providing its ID and optional section filters.

Instructions

Get the full results of a completed Sieve analysis.

Returns the Sieve Score (0-140), meeting decision (Take Meeting/Pass/ Need More Info), executive summary, key strengths, and key concerns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deal_idYesThe deal ID returned by sieve_screen.
sectionsNoComma-separated filter (e.g. 'summary,strengths,concerns'). Options: summary, profiles, findings, questions, strengths, concerns. Empty returns everything. Score and decision are always included.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for sieve_results. Decorated with @mcp.tool, it accepts deal_id and optional sections, delegates to client.results().
    @mcp.tool(
        annotations={
            "readOnlyHint": True,
            "destructiveHint": False,
            "openWorldHint": True,
        }
    )
    async def sieve_results(deal_id: str, sections: str = "") -> dict:
        """Get the full results of a completed Sieve analysis.
    
        Returns the Sieve Score (0-140), meeting decision (Take Meeting/Pass/
        Need More Info), executive summary, key strengths, and key concerns.
    
        Args:
            deal_id: The deal ID returned by sieve_screen.
            sections: Comma-separated filter (e.g. 'summary,strengths,concerns').
                      Options: summary, profiles, findings, questions, strengths, concerns.
                      Empty returns everything. Score and decision are always included.
        """
        return await client.results(deal_id, sections=sections)
  • The HTTP client helper that performs the actual API call for sieve_results. Sends GET /api/v1/public/screen/{deal_id}/results with optional sections query parameter.
    async def results(deal_id: str, sections: str = "") -> dict[str, Any]:
        """Get full results of a completed analysis."""
        query = f"?sections={sections}" if sections else ""
        return await _request("GET", f"/screen/{deal_id}/results{query}")
  • The @mcp.tool decorator on the sieve_results function registers it as an MCP tool. This is the registration mechanism.
    @mcp.tool(
        annotations={
            "readOnlyHint": True,
            "destructiveHint": False,
            "openWorldHint": True,
        }
    )
    async def sieve_results(deal_id: str, sections: str = "") -> dict:
        """Get the full results of a completed Sieve analysis.
    
        Returns the Sieve Score (0-140), meeting decision (Take Meeting/Pass/
        Need More Info), executive summary, key strengths, and key concerns.
    
        Args:
            deal_id: The deal ID returned by sieve_screen.
            sections: Comma-separated filter (e.g. 'summary,strengths,concerns').
                      Options: summary, profiles, findings, questions, strengths, concerns.
                      Empty returns everything. Score and decision are always included.
        """
        return await client.results(deal_id, sections=sections)
  • The function signature and docstring define the schema: deal_id (str, required) and sections (str, optional default '') with documented valid options.
    async def sieve_results(deal_id: str, sections: str = "") -> dict:
        """Get the full results of a completed Sieve analysis.
    
        Returns the Sieve Score (0-140), meeting decision (Take Meeting/Pass/
        Need More Info), executive summary, key strengths, and key concerns.
    
        Args:
            deal_id: The deal ID returned by sieve_screen.
            sections: Comma-separated filter (e.g. 'summary,strengths,concerns').
                      Options: summary, profiles, findings, questions, strengths, concerns.
                      Empty returns everything. Score and decision are always included.
        """
        return await client.results(deal_id, sections=sections)
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds value by detailing the return values (score, decision, summary, etc.) and the effect of the 'sections' parameter. However, it could mention error handling for invalid deal_ids.

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 two sentences long, front-loaded with purpose, and efficiently lists outputs without redundancy. Every sentence adds value.

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?

For a simple retrieval tool with an output schema, the description covers purpose, returns, and parameter usage. It could be more explicit about the dependency on a valid deal_id from sieve_screen, but overall it sufficiently informs the agent.

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?

Input schema has 100% coverage with descriptions for both parameters. The description does not add new information about parameters beyond what the schema provides, but it contextualizes the 'sections' parameter by listing filter options.

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: 'Get the full results of a completed Sieve analysis.' It lists specific outputs (Sieve Score, meeting decision, executive summary, etc.), making it distinct from sibling tools like sieve_screen which starts the analysis.

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

Usage Guidelines3/5

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

The description implies the tool should be used after a completed Sieve analysis, but it does not explicitly state when to use it versus alternatives (e.g., sieve_screen) or provide exclusions. No direct guidance on prerequisites or conditions.

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