Update an existing proxy server configuration in Security Director Cloud by specifying its UUID and a JSON body matching the target schema.
Update a proxy server object by UUID.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON request body matching the target Security Director Cloud schema. | |
| uuid | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description only states 'update' without disclosing mutation behavior, idempotency, required state (e.g., object existence), side effects, or response format. Behavioral expectations are entirely implicit.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with no wasted words. Front-loaded with verb and resource. Concise enough for quick scanning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given complexity (nested body parameter, sibling tools for config), description lacks details on partial vs full updates, allowed fields in body, and whether update triggers deployment. Output schema absent, but description could still explain return value. Overall insufficient for a nuanced update operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has 2 parameters with 50% coverage (body has a generic description referencing the target schema, uuid lacks description). The tool description adds no additional parameter meaning beyond what schema provides. Schema coverage alone gives baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Update a proxy server object by UUID' with specific verb and resource. It distinguishes from sibling CRUD operations (create, get, list, delete). However, it does not elaborate on what aspects can be updated, which would add clarity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like sdcloud_set_proxy_server_config. No mention of prerequisites or contexts where update is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.