Skip to main content
Glama
Sign In

Nebelus

by ai.nebelus.api
OverviewDiscussionsAdmin

Create policy from template

create_policy_from_template

Create a DRAFT policy from a template. The template only sets the starting point: validation_points and configuration_overrides change this policy, never the template.

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": {
      "template_id": "<template_id>"
    },
    "name": "create_policy_from_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPolicy name (defaults to the template's).
descriptionNoPolicy description.
template_idYesId from list_policy_templates.
validation_pointsNoWhich side the policy checks: input = messages users send, output = replies the agent writes, both (default when unset). Only for data_privacy, content_filter, output_validation, custom.
configuration_overridesNoConfiguration keys to change for this policy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write-and-safe profile is covered; the description adds genuinely useful non-obvious behavior: the result is a DRAFT and edits do not propagate to the shared template. It does not say whether the new policy must be activated separately or what permissions are required.

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?

Two sentences, both front-loaded with the most important information (creation is a DRAFT, template is read-only during this call). No 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 5-parameter create tool with one required field, full schema coverage and a nested object, the description covers the essential lifecycle detail (DRAFT) and the non-mutation guarantee. It leaves the shape of configuration_overrides and the returned identifier unexplained, but no output schema exists and the schema text covers the scalar params.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: validation_points and configuration_overrides override the created policy rather than mutating the template, which the per-parameter schema text does not convey. The nested configuration_overrides object's key structure remains unexplained in either place.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a DRAFT policy') plus the source ('from a template'), and the DRAFT qualifier is a meaningful scope detail. It doesn't explicitly contrast with the sibling create_governance_policy (create-from-scratch), so the distinction is implied rather than named.

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

Usage Guidelines3/5

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

Usage is implied by the existence of list_policy_templates (referenced through the template_id schema description) and by 'from a template', but the description never states when to choose this over create_governance_policy or what prerequisites exist. An agent must infer the routing.

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

All Nebelus toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources