Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_dns_list_locations

List all DNS Protection locations for a specified tenant, with filters for name, type, IP, and domain.

Instructions

List all DNS Protection locations for a tenant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter locations by exact name
pageNoPage number, starting with 1
sortNoSort field (e.g. name, createdAt)
typeNoFilter by location type
page_sizeNoResults per page
tenant_idYesTenant UUID
is_defaultNoFilter by whether the location is the default
page_totalNoWhether to calculate and return total page count
domain_namesNoFilter locations associated with this domain name
name_containsNoFilter locations whose name contains this substring
ip_addresses_containsNoFilter locations containing this IP address
Behavior2/5

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

Without annotations, the description must convey behavioral aspects. It fails to mention that this is a read-only operation, that results are paginated (implied by schema but not stated), or any rate limits or prerequisites beyond tenant_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but overly minimal. It could include more useful information without being verbose.

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 large number of parameters and no output schema, the description lacks completeness. It does not explain what a DNS Protection location is, how filters work together, or what the response contains.

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%, so baseline is 3. The description adds no additional meaning beyond the schema for the 11 parameters.

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 verb 'list', the resource 'DNS Protection locations', and the scope 'for a tenant'. It effectively distinguishes from sibling DNS list tools (e.g., sophos_dns_list_custom_domains) by specifying the exact resource type.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when to filter, paginate, or compare with sophos_dns_get_location for specific locations.

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