codearia-sieve
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sieve_pageA | Turns a web page into decision-ready state: dates as ISO fields, numbers with units as facts, text in token-budgeted chunks with anchors back to the page, and the token bill (raw vs state). Start with mode=summary; fetch chunk text with sieve_chunk or mode=full only when needed. |
| sieve_chunkA | Returns the text of a chunk from a page prepared earlier with sieve_page (same url). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: sieve_page processes a web page into chunks and metadata, while sieve_chunk retrieves the text of a specific chunk. There is no overlap or ambiguity—an agent can easily decide which tool to call based on whether it needs to prepare a page or access its content.
Both tools follow the same verb_noun pattern with the 'sieve_' prefix: sieve_page and sieve_chunk. The naming is perfectly consistent, making the toolset predictable and intuitive.
With only 2 tools, the server feels minimal for the stated purpose of turning web pages into decision-ready state. While the core workflow (prepare and fetch chunks) is covered, the narrow surface may not justify a full server; however, it is within the borderline range where it could be acceptable for a very focused utility.
The primary lifecycle is complete: sieve_page prepares a page and sieve_chunk retrieves its content. Minor gaps exist—such as lacking a way to list already-prepared pages or clear cached data—but these are not critical and can be worked around by tracking URLs externally. The inclusion of mode=full also provides an alternative to chunk retrieval, though it overlaps slightly.