Skip to main content
Glama
MSPbotsAI

cisco-umbrella-mcp

by MSPbotsAI

cisco_umbrella_get_activity_proxy

Retrieve proxy activity events from Cisco Umbrella's Secure Web Gateway. Filter by domains, URLs, verdict, threats, or time range to investigate web traffic and security incidents.

Instructions

List proxy (Secure Web Gateway) activity events.

    API: GET /reports/v2/activity/proxy

    Args:
        from_: Required. Start of the time range. Accepts epoch
            milliseconds, ISO-8601 (e.g. "2024-01-01T00:00:00Z"), or a
            relative offset (e.g. "-1days", "-7days", "now").
        to: Required. End of the time range. Same accepted formats as from_.
        limit: Max results per page (default 100).
        offset: Pagination offset.
        domains: Comma-separated domain filter.
        urls: Comma-separated URL filter.
        categories: Comma-separated content category ID filter.
        identityids: Comma-separated identity ID filter.
        verdict: Filter by verdict, e.g. "allowed" or "blocked".
        threats: Comma-separated threat name filter.
        filename: Filter by downloaded file name.
        timezone: IANA timezone name for the response's time fields.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes
urlsNo
from_Yes
limitNo
offsetNo
domainsNo
threatsNo
verdictNo
filenameNo
timezoneNo
categoriesNo
identityidsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the HTTP method (GET) and details about timezone handling and pagination, which is useful. However, it does not explicitly state that this is a read-only operation, mention authentication requirements, or describe error behavior, leaving some gaps.

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 well-structured docstring with the API endpoint followed by an Args list. Each parameter gets a single concise line, and the content is front-loaded with the core action. No wasted 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?

Despite having 12 parameters and no schema descriptions, the description covers every parameter, the API endpoint, and special formatting details for time fields and timezone. An output schema exists, so return values are presumably covered there. It is complete for a reporting tool of this complexity.

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?

Schema description coverage is 0%, so the description fully compensates by explaining every parameter, including accepted formats for from_/to (epoch, ISO-8601, relative offsets), default values, and filter semantics with examples (e.g., verdict 'allowed' or 'blocked'). This adds substantial meaning beyond the raw schema.

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 it 'List proxy (Secure Web Gateway) activity events', providing a specific verb and resource. The term 'proxy' differentiates it from sibling tools that focus on DNS, firewall, or AMP activities.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives like DNS or firewall activity tools. While the name and description imply proxy/SWG reporting, there are no when-to-use or when-not-to-use statements, and no alternatives are mentioned.

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/MSPbotsAI/cisco-umbrella-mcp'

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