Skip to main content
Glama
Sign In
aegis

aegis

by Acacian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_policy

Update the governance policy by providing a new YAML string. Changes take effect immediately for all subsequent evaluations.

Instructions

Hot-reload the governance policy from a YAML string.

    The new policy takes effect immediately for all subsequent evaluations.

    Args:
        yaml_content: YAML string containing the policy rules.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "yaml_content": "<yaml_content>"
    },
    "name": "update_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
yaml_contentYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

The description states the effect: 'takes effect immediately for all subsequent evaluations,' which provides behavioral transparency. Since no annotations are provided, the description carries the full burden, and it adequately conveys the impact.

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 concise with two sentences and an Args section, front-loaded with the main action. No unnecessary information.

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?

Given that an output schema exists and the tool is simple, the description covers the input and effect adequately. It could mention error handling or validation but is mostly complete.

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

Parameters4/5

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

The description includes an Args section that explains the yaml_content parameter as 'YAML string containing the policy rules,' adding meaning beyond the schema, which has 0% description coverage.

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 tool's purpose: 'Hot-reload the governance policy from a YAML string.' It specifies the verb (hot-reload), resource (governance policy), and input (YAML string), distinguishing it from sibling tools like check_risk, evaluate_action, evaluate_batch, and get_policy.

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 mentions that the new policy takes effect immediately, implying real-time usage. However, it does not provide explicit guidance on when to use this tool versus alternatives or when not to use it.

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