Skip to main content
Glama
Heretek-RE

re-leak-scan

by Heretek-RE

verify_sentry_dsn

Parse a Sentry DSN and probe the host to confirm reachability, returning parsed details and verification status.

Instructions

Parse a Sentry DSN and (if httpx is available) probe the Sentry host to confirm reachability.

Args: dsn: a single Sentry DSN string (the full URL, including the https://key@host/project_id form)

Returns::

{"dsn": "...", "parsed": {"host": "...", "project_id": N,
                           "public_key": "..."},
 "verified": bool, "http_status": N | None, "reason": "..."}

The probe hits <host>/api/0/projects/<org>/<project>/ with the public key. A 200/401/403/404 means the endpoint is reachable (the specific status tells you whether the key has project access). A connection error or timeout means the host is unreachable from the analyst's network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dsnYes
Behavior5/5

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

With no annotations, the description fully discloses behavior: it parses the DSN, optionally probes the host, explains HTTP status meanings, and notes the httpx dependency. This is comprehensive for a simple tool.

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?

The description is well-structured with clear sections (purpose, Args, Returns, explanation). It is slightly lengthy but every sentence adds value, and the main action is front-loaded.

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

Completeness5/5

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

Despite lacking an output schema, the description details the return format with an example and explains the probe logic. For a single-parameter tool, this is complete and leaves no ambiguity.

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

Parameters5/5

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

The input schema has zero description coverage for the 'dsn' parameter. The description adds critical meaning by specifying the exact format (full URL with https://key@host/project_id) and explaining it is a single DSN string, compensating fully for the schema gap.

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 explicitly states it parses a Sentry DSN and probes the Sentry host for reachability. This specific verb+resource combination clearly distinguishes it from sibling tools, which focus on different tasks like leak scanning or string extraction.

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 does not provide explicit guidance on when to use this tool over alternatives or mention contraindications. It implies usage when a Sentry DSN needs verification, but no comparative context is given.

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/Heretek-RE/re-leak-scan'

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