Skip to main content
Glama
AtlaSent-Systems-Inc

atlasent-mcp

Official

AtlaSent — Revoke Permit

atlasent_revoke_permit

Revoke a permit to invalidate it immediately for verification calls, before its scheduled expiration.

Instructions

Revoke a permit before it expires. The permit immediately becomes invalid for verify_permit calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
org_idYesOrganization ID that owns the permit.
reasonsNoHuman-readable reasons for revocation.
permitTokenYesThe permit token to revoke.
Behavior1/5

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

Description states the permit becomes invalid, indicating a destructive operation. But annotations have destructiveHint: false, contradicting the description. Therefore score is 1 due to contradiction.

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, each adding value. First sentence states purpose, second adds behavioral detail. No fluff.

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 simple revocation tool, the description covers main purpose and effect. Could include more about error conditions or prerequisites, but overall adequate given low complexity.

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 description coverage is 100%, so baseline is 3. The description does not add any additional meaning beyond the schema.

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?

Description clearly states the verb 'revoke', the resource 'permit', and the effect (immediately invalid for verify_permit). It distinguishes from siblings like atlasent_permit and atlasent_verify_permit.

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?

Description says 'Revoke a permit before it expires', providing context for when to use it. However, it does not explicitly mention when not to use it or alternatives.

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