AI SENSE Free Public Tools

Acquire lease

acquire_lease

Claim one unit of work so concurrent agents do not perform it twice. The first writer receives an owner token and a monotonic fencing token. A later caller receives held, conflict or a reusable completed result. Contention is a normal result. Use a private namespace, or supply a high-entropy unscoped key. No authentication is required.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	Yes	Work identity. With a namespace it may be a short URL-safe name. Without one it must be a caller-generated high-entropy secret of at least 32 characters.
`namespace`	No	Optional 256-bit namespace from create_lease_namespace. Keep it secret.
`fingerprint`	No	Optional stable description or digest that binds this key to the same work.
`ttl_seconds`	No	Ownership period, capped by the absolute 24 hour lifetime.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`result`	No
`status`	Yes
`owner_token`	No
`ttl_seconds`	No
`completed_at`	No
`fencing_token`	No
`lease_expires_at`	No
`absolute_expires_at`	No
`retry_after_seconds`	No
`completed_at_timestamp`	No
`lease_expires_at_timestamp`	No
`absolute_expires_at_timestamp`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedSep 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only indicate the tool is not read-only, not idempotent, and not destructive, so the description carries the burden and meets it well. It discloses first-writer token outcomes, later-caller conflict/completed outcomes, contention as a normal result, and the fact that no authentication is 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?

Four short sentences, each carrying distinct useful information: purpose, result variants, contention handling, and key/auth guidance. The main claim is front-loaded with no filler.

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?

The essentials for selecting and invoking the tool are present: what it does, expected outcomes, contention guidance, and key strategy. Output schema covers return shape. It omits explicit handoff to renew/complete/release and TTL-expiry behavior, but these are secondary for a correct initial call.

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% and the parameter descriptions are already rich, including key length constraints, namespace pattern, and TTL bounds. The description reinforces the private-namespace/high-entropy-key strategy but adds little beyond what the schema already documents.

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?

States a specific verb-resource pair — 'Claim one unit of work' — and explains the goal: preventing concurrent agents from performing the same work twice. The acquired-vs-completed/released lifecycle clearly distinguishes it from siblings like complete_lease and release_lease even without naming them.

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?

Provides clear invocation context: claim exclusive work in a concurrent environment, expect contention as normal, and choose a private namespace or high-entropy unscoped key. It doesn't explicitly contrast with renew/complete/release siblings, but the usage context is unmistakable.

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

All AI SENSE Free Public Tools tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool belongs to a clearly separated resource family: leases, heartbeats, human approvals, webhook captures, temporary data, and small utilities. Even similar-sounding tools like create_agent_wake and create_heartbeat are differentiated by their descriptions: durable task completion versus deadline monitoring.

Naming Consistency5/5

Tool names consistently use a snake_case verb_noun pattern, such as acquire_lease, create_heartbeat, read_webhook_capture, and store_temporary_data. Paired operations read naturally, with only a minor and acceptable variation between get_current_time and the read_* tools.

Tool Count4/5

At 18 tools, this is slightly above the ideal 3-15 range, but the server intentionally bundles several independent public utilities rather than one narrow domain. Each tool has a distinct purpose, so the count feels full but not bloated.

Completeness4/5

Core workflows are well covered: leases support acquire, renew, release, and complete; heartbeats support create, ping, and read; captures, approvals, and temporary data have create/read or store/read pairs. There are no explicit delete, cancel, or update tools, but the 24-hour expiration design makes those gaps manageable.

Acquire lease

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources