Skip to main content
Glama
AtlaSent-Systems-Inc

atlasent-mcp

Official

AtlaSent — Create Policy

atlasent_create_policy

Create a draft policy bundle to define rules for access control or approval gates. Publish it with update_policy.

Instructions

Create a new constraint bundle for an action. The bundle starts in 'draft' status — call update_policy to publish it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rulesYesOrdered list of rules — first match wins.
titleYesHuman-readable policy title.
org_idYesOrganization ID that will own the policy.
actionsNoAction-specific configuration.
versionNoSemantic version string (e.g. '1.0.0').
priorityNoEvaluation priority (lower number = higher priority).
policy_idYesClient-assigned unique ID for this policy bundle (e.g. 'deploy-gate').
applies_toNoScope selector controlling which requests this policy applies to.
expires_atNoISO-8601 timestamp when the policy expires.
descriptionNoOptional human-readable description.
policy_typeYesPolicy type (e.g. 'access_control', 'approval_gate').
effective_atNoISO-8601 timestamp when the policy becomes effective.
Behavior4/5

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

Annotations indicate a non-read-only, non-destructive operation. The description adds that the bundle starts as a draft, a key behavioral detail. No contradictions.

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 concise sentences, front-loaded with core purpose and a critical follow-up instruction. No unnecessary words.

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

Completeness3/5

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

Despite schema completeness, the description is minimal for a tool with 12 parameters and nested objects. It lacks broader context about actions or constraint bundles, making it adequate but not comprehensive.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for all parameters. The description does not add additional semantics beyond the schema, so baseline score applies.

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 states 'Create a new constraint bundle for an action', clearly identifying the verb and resource. It distinguishes from siblings by mentioning the draft status and directing to update_policy for publishing.

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 explains when to use this tool (create new policy) and what to do after (update_policy to publish). It does not explicitly exclude other use cases but provides clear context.

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/AtlaSent-Systems-Inc/atlasent-mcp-server'

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