Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_create_partner_role

Create a partner-level role by specifying a name, optional description, and permission sets to define access rights for MSP operations.

Instructions

Create a new partner-level role with the specified name and permission sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRole name
descriptionNoRole description
permission_set_idsNoComma-separated permission set UUIDs to include in this role. Use sophos_list_permission_sets to see available permission sets.
Behavior3/5

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

Annotations already indicate readOnlyHint=false (write) and destructiveHint=false. The description adds 'partner-level' context but lacks details on side effects or required permissions. No contradiction.

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?

Single sentence that efficiently conveys the purpose with no fluff.

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?

Missing return value description (creates a role but no mention of what is returned). Lacks usage context and prerequisites. Not fully informative for an agent.

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 covers all parameters fully (100% coverage). Description only reiterates 'name and permission sets' without adding new meaning beyond the 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 the verb 'create' and the resource 'partner-level role', distinguishing it from sibling tools like sophos_create_tenant_role.

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 on when to use this tool versus alternatives, such as sophos_create_tenant_role or admin role assignments. No prerequisites or context provided.

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