Skip to main content
Glama
Sign In
sieve-map

sieve-map

by gautam-u
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

sieve_check_text

Check text for secrets; returns boolean only without echoing input or detected values.

Instructions

Checks whether text contains secrets. Returns boolean only — never echoes input or detected values.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "sieve_check_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to check for secrets

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral trait (never echoes input or detected values), which is critical for privacy-sensitive tools. However, it does not mention other aspects like performance, rate limits, or error behavior.

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 a single, well-structured sentence that conveys purpose and key behavior without any redundant information.

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?

Given the tool's simplicity (one parameter, no output schema), the description is nearly complete. It covers purpose, return type, and a privacy promise. It could be slightly improved by hinting at what constitutes a 'secret', but overall it is sufficient.

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?

Schema coverage is 100%, and the schema description for 'text' already states 'Text to check for secrets'. The description adds minimal extra parameter meaning beyond the schema, so baseline of 3 is appropriate.

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 checks text for secrets, and distinguishes it from sibling tools like sieve_redact_text (which redacts) and sieve_findings_list (which lists findings). The verb 'checks' and resource 'text' are specific and unambiguous.

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 usage context by stating it returns only a boolean and never echoes input, suggesting it is for binary secret detection rather than detailed analysis. However, it does not explicitly state when to use or avoid this tool versus alternatives like sieve_findings_list or sieve_redact_text.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools