Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_list_firewalls

Retrieve a paginated list of managed firewalls from a Sophos Central tenant. Filter by group or search text to find specific firewalls.

Instructions

List all managed firewalls in a Sophos Central tenant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number to fetch, starting with 1
searchNoFree-text search across firewall fields
group_idNoFilter by firewall group ID, or 'ungrouped' for firewalls not in any group
page_sizeNoNumber of results per page (default 100)
tenant_idYesTenant UUID
page_totalNoWhether to calculate and return the number of pages
Behavior2/5

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

No annotations are present, and the description fails to mention that results are paginated or detail the return format, leaving critical behavioral aspects undocumented.

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 a single, focused sentence that front-loads the action, but it is extremely brief and could include more useful context without losing conciseness.

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

Completeness2/5

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

Given the lack of output schema and the presence of pagination parameters, the description should explain pagination behavior and result structure, which it does not.

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?

All parameters are described in the input schema (100% coverage), so the description adds no additional semantic value beyond the 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 clearly states the tool lists managed firewalls in a Sophos Central tenant, but does not explicitly distinguish from sibling tools like sophos_list_firewall_groups.

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?

No guidance is provided on when to use this tool versus alternatives such as sophos_get_firewall or sophos_list_firewall_groups.

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/rijul170/sophos-central-mcp'

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