sieve-map
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sieve_health_statusA | Returns Sieve service health and finding counts. |
| sieve_self_testB | Verifies scanner rules and transcript source coverage are healthy. |
| sieve_findings_listA | Lists findings from the most recent scan. Previews are redacted — no plaintext secret values. |
| sieve_issue_listA | Lists scanner health issues: unreadable sources, permission errors, parse failures. |
| sieve_scan_historyC | Returns past scan job summaries. |
| sieve_scan_statusA | Returns status of the current or most recent scan: idle, running, completed, or failed. |
| sieve_check_textA | Checks whether text contains secrets. Returns boolean only — never echoes input or detected values. |
| sieve_redact_textB | Redacts secrets from text, replacing values with sieve:// placeholders. Raw values are never returned. |
| sieve_vault_runA | Executes a command with macOS Keychain-resolved secrets injected as env vars. Returns exit code and line counts only — stdout/stderr content is never returned. |
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 9 tools
Each tool targets a distinct function: check vs redact text, list findings, health, issues, scan history/status, self-test, and vault run. No two tools have overlapping purposes, ensuring clear differentiation for an agent.
All tools share the 'sieve_' prefix and use snake_case, which is good. However, the part-of-speech order varies: some are verb_noun (check_text, redact_text), others are noun_noun (findings_list, health_status). This minor inconsistency prevents a perfect score.
With 9 tools, the server covers its core domain (secrets scanning and vault management) without bloat. Each tool addresses a specific need, and the count feels well-scoped for the functionality offered.
The tool set covers essential operations: checking, redacting, listing findings, health, issues, scan history/status, self-test, and vault execution. A minor gap is the absence of a tool to trigger a scan or manage vault entries, but the core workflows are supported.