Skip to main content
Glama
sifter-ai

sifter-mcp

Official

get_sift

Retrieve metadata and extraction schema for a specific sift to understand its typed record structure and fields.

Instructions

Get sift metadata and inferred extraction schema for a specific sift.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sift_idYes

Implementation Reference

  • The MCP tool handler for 'get_sift'. Decorated with @mcp.tool(), it asynchronously gets a sift by ID via the SDK client and returns its data dict.
    @mcp.tool()
    async def get_sift(sift_id: str) -> dict:
        """Get sift metadata and inferred extraction schema for a specific sift."""
        async with _get_client() as client:
            handle = await client.get_sift(sift_id)
        return handle._data if hasattr(handle, "_data") else {"sift_id": sift_id}
  • Input schema: the tool accepts a single `sift_id: str` parameter.
    async def get_sift(sift_id: str) -> dict:
  • Registered as an MCP tool via the `@mcp.tool()` decorator on the `get_sift` async function.
    @mcp.tool()
  • SDK helper - `AsyncSifter.get_sift()` makes the actual HTTP GET request to `/api/sifts/{sift_id}` and returns an AsyncSiftHandle.
    async def get_sift(self, sift_id: str) -> AsyncSiftHandle:
        async with httpx.AsyncClient() as http:
            r = await http.get(
                f"{self.api_url}/api/sifts/{sift_id}",
                headers=self._auth_headers(),
            )
            r.raise_for_status()
            return AsyncSiftHandle(r.json(), self)
  • SDK helper - synchronous `Sifter.get_sift()` makes HTTP GET request to `/api/sifts/{sift_id}`.
    def get_sift(self, sift_id: str) -> SiftHandle:
        """Get a handle to an existing sift."""
        import httpx
        with httpx.Client() as http:
            r = http.get(
                f"{self.api_url}/api/sifts/{sift_id}",
                headers=self._auth_headers(),
            )
            r.raise_for_status()
            return SiftHandle(r.json(), self)
Behavior2/5

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

No annotations provided, so description must carry the burden. It only states the operation is a get, but does not disclose read-only nature, authentication needs, error behavior, or any side effects.

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?

Single sentence, directly front-loads the action and object. No wasted words, but lacks necessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and simple parameters, the description is incomplete. It omits what the response contains, error scenarios, and relationships to sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and description adds no meaning to the sole parameter sift_id. It does not explain format, type, or constraints 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 verb 'Get' and the resource 'sift metadata and inferred extraction schema'. It specifies the target is a specific sift, distinguishing it from list_sifts and other sibling tools.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, no when-not scenarios mentioned. The description only states what it does, not the context.

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/sifter-ai/sifter'

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