Skip to main content
Glama

bardo_policy_set

Idempotent

Propose a security policy change. Tightening applies immediately; loosening is queued with a delay. Requires solving a challenge puzzle to authorize.

Instructions

Propose a change to your security policy. Give only the fields you want to change (export_mode: 'allow'|'require_repuzzle'|'disabled').

A change that only tightens (e.g. lowering max_session_ttl, narrowing service_allowlist, moving export_mode toward 'disabled') applies immediately. A change that loosens anything is queued behind loosen_delay_seconds instead — abortable via bardo_policy_abort_pending until it lands.

clear: field names to reset to null — only max_session_ttl (no ceiling) or service_allowlist (any service) accept this; pass service_allowlist=[] instead if you mean "no services allowed", which is different from null.

Requires a step-up puzzle. If challenge_id and answer are omitted, a fresh puzzle is returned — solve it yourself, then call this tool again with your desired fields plus challenge_id and answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clearNo
answerNo
export_modeNo
challenge_idNo
session_tokenNo
tags_encryptedNo
max_session_ttlNo
service_allowlistNo
delete_grace_secondsNo
loosen_delay_secondsNo
Behavior5/5

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

Annotations provide idempotentHint=true and destructiveHint=false. The description adds detailed behavioral context: tightening applies immediately, loosening is delayed and abortable, and a step-up puzzle may be required. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer but front-loaded with purpose and behavioral details. Every sentence adds value, though it could be slightly more concise. No wasted words.

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 the complexity (10 parameters, step-up puzzle, delayed vs immediate), the description covers the main flow and key parameters. It references sibling tools for abort and read. No output schema, but the description doesn't need to detail return values for input-focused tool.

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?

With 0% schema description coverage, the description compensates well by explaining key parameters: export_mode (allowed values), clear (semantics), max_session_ttl, service_allowlist, challenge_id, and answer. Some parameters (tags_encrypted, delete_grace_seconds, loosen_delay_seconds) are not explicitly covered, but the core ones are.

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 'Propose a change to your security policy' with a specific verb and resource. It differentiates from siblings like bardo_policy_get (read) and bardo_policy_abort_pending (abort).

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

Usage Guidelines5/5

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

The description explains when to use (changing policy), distinguishes tightening vs loosening with immediate vs delayed application, and references the abort mechanism via bardo_policy_abort_pending. It also explains the step-up puzzle requirement.

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/calebe/bardo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server