Skip to main content
Glama
AIops-tools

endpoint-aiops-mcp

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

endpoint_assign_profile

Assign a config profile to an endpoint while preserving the previous profile for audit and rollback. Use dry_run to preview the replacement before applying.

Instructions

[WRITE][risk=high] Assign a config profile to an endpoint (reversible).

Captures the prior profile before switching, so the harness records an undo (reassign the prior profile) and a faithful audit trail. Pass dry_run=True to preview: it resolves the same path and reads the same before-state as the real call, so it reports the profile that would actually be replaced and refuses on the same grounds the write would.

Args: endpoint_id: Endpoint id as returned by endpoint_list. profile_id: Config profile to assign. dry_run: If True, preview without assigning. target: Endpoint-management target name from config; omit for the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNo
dry_runNo
profile_idYes
endpoint_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.3
    • addedInput schema / properties / dry_run
      Added value: +{
+  "default": false,
+  "title": "Dry Run",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are present, but the description supplies the safety profile itself: it is a write, high risk, reversible, captures the prior profile for an undo and audit trail, and dry-run resolves the same path and before-state while refusing on the same grounds as the real call. This is exceptionally transparent.

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?

The description is front-loaded with the [WRITE][risk=high] tag and a one-line summary, followed by a tight dry-run explanation and a concise Args block. Every sentence adds useful information without filler or redundancy.

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

Completeness4/5

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

For a high-risk write tool with no annotations and no output schema, the description covers behavior, reversibility, undo/audit trail, dry-run behavior, and argument provenance. It is slightly incomplete in not describing the success response or explicit error conditions beyond the dry-run refusal scenario.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the Args section fully compensates for all four parameters. It explains dry_run semantics, endpoint_id provenance via endpoint_list, the meaning of profile_id, and the target source/config default behavior beyond what the schema states.

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 opening line names a specific action (assign), the resource (config profile), and the destination (endpoint), and marks it as a write/reversible operation. This makes it immediately distinguishable from sibling read tools like endpoint_get and maintenance actions like endpoint_reboot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear operational guidance for using dry_run=True as a preview versus the real write, and explains that endpoint_id comes from endpoint_list and target can be omitted for the default. It does not explicitly name alternatives such as undo_apply or state when not to use this tool, so it misses the top anchor of 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools