Skip to main content
Glama
wyre-technology

abnormal-mcp

abnormal_navigate

Select a domain to discover available Abnormal Security tools: threats, messages, remediation, abuse, or cases. Returns tool names and descriptions for each area.

Instructions

Discover available Abnormal Security 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: - threats: Threat detection — list and inspect detected threat cases - messages: Message analysis — list and inspect individual emails within a threat - remediation: Remediation — trigger or check email remediation actions - abuse: Abuse mailbox — list phishing emails reported by users - cases: Security cases — list and inspect analyst investigation cases
Behavior3/5

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

No annotations provided, so description carries burden. It clearly states it's a read-only discovery aid with no side effects. Could explicitly mention read-only nature, but adequate.

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?

Two concise sentences, front-loaded with purpose. No fluff.

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

Completeness3/5

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

For a simple tool with one parameter and no output schema, the description is complete. It explains what it does and its optional nature.

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% with enumerated values and descriptions. The description adds the context that the parameter selects a domain, but no additional semantics beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool discovers available tools by domain and returns names and descriptions. It distinguishes itself from sibling operational tools by being a discovery aid.

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 notes that all tools are callable at any time and this is not a prerequisite, giving some usage context. However, it doesn't specify when to use this vs directly calling a domain-specific tool.

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/abnormal-mcp'

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