Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_update_tenant_admin

Update a tenant administrator's first name, last name, or email address for a specified tenant and admin ID.

Instructions

Update a tenant administrator's details (name or email).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoUpdated email address
admin_idYesAdmin UUID
last_nameNoUpdated last name
tenant_idYesTenant UUID
first_nameNoUpdated first name
Behavior3/5

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

Description (update) aligns with annotations (readOnlyHint=false). No additional behavioral context beyond mutation; does not disclose side effects, idempotency, or permission requirements. Annotations already indicate write operation.

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, 9 words, front-loaded with verb 'Update'. Every word earns its place; no waste.

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?

No output schema, but description does not mention return value, error handling, or what happens on partial updates. Lacks completeness for a 5-param write operation.

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 descriptions for all 5 params. Description adds only a summary ('name or email'), not extending meaning beyond schema. Baseline 3 applies.

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?

Description clearly states the verb 'Update' and resource 'tenant administrator's details', specifying updatable fields ('name or email'), distinguishing from create/list siblings.

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 (e.g., sophos_create_tenant_admin, sophos_get_tenant_admin). Does not mention prerequisites or when to prefer this over other admin tools.

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