Skip to main content
Glama
wyre-technology

proofpoint-mcp

proofpoint_navigate

Discover Proofpoint tools for a selected domain. Returns tool names and descriptions to help you identify available capabilities.

Instructions

Discover available Proofpoint tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain to explore: - tap: Targeted Attack Protection (TAP) - SIEM API for threats, clicks, messages, and attack intelligence - quarantine: Quarantine management - list, release, delete, and search quarantined email messages - threat_intel: Threat intelligence - IOCs, threat families, campaigns, and security indicators - dlp: Data Loss Prevention & email encryption - manage sensitive data protection policies - people: User risk scoring and Very Attacked People (VAP) reports - identify high-risk users - forensics: Forensics and threat response - auto-pull, search & destroy malicious content - smart_search: Message tracing / Smart Search - track email delivery and routing - policy: Policy management - configure email security rules and enforcement - url_defense: URL Defense - URL decoding, analysis, and malicious link protection - events: Security events - spam, phishing, and malware detection alerts - reports: Organization-level security reports - threat summaries and analytics
Behavior4/5

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

With no annotations, the description carries the burden of transparency. It discloses that the tool is a non-essential discovery aid with no side effects, and that tools are callable regardless. It doesn't detail error conditions, but for a help tool this is sufficient.

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?

Three short sentences that are front-loaded with the action, then output, then usage caveat. No filler words.

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?

For a simple help/discovery tool with a single well-documented parameter and no output schema, the description covers purpose, output, and usage context. The agent knows exactly what to expect.

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?

The schema already provides 100% coverage, including descriptions for each enum value. The description adds no extra semantic details about the 'domain' parameter, simply referring to 'the selected domain.'

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's function: 'Discover available Proofpoint tools by domain' and specifies it 'Returns tool names and descriptions for the selected domain.' This distinguishes it from sibling operation tools as a discovery/navigation aid.

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

Usage Guidelines4/5

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

It explicitly states when not to use it as a prerequisite: 'All tools are callable at any time — this is a help/discovery aid, not a prerequisite.' It implies the use case of exploring available tools in a chosen domain, but doesn't name specific alternatives.

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/wyre-technology/proofpoint-mcp'

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