AI SENSE Free Public Tools

Renew lease

renew_lease

Extend a lease that this caller still owns. Use it before the current TTL ends when work is still running. The owner token is required and must stay secret. Renewal cannot move the absolute 24 hour limit. 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.
`owner_token`	Yes	Secret owner token returned by acquire_lease.
`ttl_seconds`	No

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.1/5.0

Behavior4/5

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

Annotations only indicate non-read-only, non-idempotent, and non-destructive behavior. The description adds the ownership condition, owner-token secrecy, the absolute 24-hour cap, and the fact that no authentication is required, all beyond what annotations provide.

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?

Five short sentences, each carrying distinct information, with purpose and usage front-loaded. There is no fluff, though some clauses could be combined.

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?

Covers the timing, ownership condition, owner-token requirement, absolute limit, and auth expectation for a simple lease-renewal operation. Since an output schema exists, return-value details are not required from the description.

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?

The schema already documents key, namespace, and owner_token well; the description reinforces owner_token secrecy and adds the 24-hour limit that constrains ttl_seconds. However, ttl_seconds itself is not explicitly explained in the description, and key/namespace receive no additional semantic guidance.

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 concrete verb and resource, 'Extend a lease that this caller still owns,' which clearly differentiates it from lifecycle siblings like complete_lease and release_lease. The title 'Renew lease' is expanded meaningfully rather than merely repeated.

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?

Gives a clear trigger: 'Use it before the current TTL ends when work is still running.' It does not explicitly name alternatives such as complete_lease or release_lease, so it stops short of full when-not guidance.

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.

Renew lease

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources