Skip to main content
Glama

Vigil — an outside witness for AI agents

by com.vigilnotary
OverviewDiscussionsAdmin

vigil_renew_lease

Destructive

Extend a lease with a fresh signed token and new expiry. Renewing is how a healthy agent keeps acting; stop renewing (or revoke) and it lapses. Security-sensitive: extends authority and refreshes the offline recheck window. Keep renewal credentials outside the controlled agent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ttl_sYesRequested lease lifetime in seconds, 5..604800; offline trust still ends at recheck_by_ms within 30 seconds.
lease_idYesOpaque lease identifier returned by vigil_grant_lease.
vigil_keyNoDEPRECATED legacy account-wide credential, including deletion and permission issuance. Prefer the client-injected HTTP Authorization: Bearer header; omit this argument when that header authenticates the request. This is not a scoped agent token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / examples
      Added value: +[
+  {
+    "lease_id": "lease_example",
+    "ttl_s": 60
+  }
+]
    • addedInput schema / properties / lease_id / description
      Added value: +"Opaque lease identifier returned by vigil_grant_lease."
    • addedInput schema / properties / lease_id / maxLength
      Added value: +128
    • addedInput schema / properties / lease_id / minLength
      Added value: +1
    • addedInput schema / properties / ttl_s / description
      Added value: +"Requested lease lifetime in seconds, 5..604800; offline trust still ends at recheck_by_ms within 30 seconds."
    • addedInput schema / properties / ttl_s / maximum
      Added value: +604800
    • addedInput schema / properties / ttl_s / minimum
      Added value: +5
    • addedInput schema / properties / vigil_key / deprecated
      Added value: +true
    • changedInput schema / properties / vigil_key / description
      Previous value: -"Legacy credential argument. Prefer the HTTP Authorization: Bearer header; omit this argument when that header authenticates the request."New value: +"DEPRECATED legacy account-wide credential, including deletion and permission issuance. Prefer the client-injected HTTP Authorization: Bearer header; omit this argument when that header authenticates the request. This is not a scoped agent token."
    • addedInput schema / properties / vigil_key / maxLength
      Added value: +256
    • addedInput schema / properties / vigil_key / minLength
      Added value: +1
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark this as mutating and destructive; the description adds useful context by noting it 'extends authority and refreshes the offline recheck window,' is security-sensitive, and requires keeping renewal credentials outside the controlled agent. No contradiction 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.

Conciseness5/5

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

Three tightly written sentences with the core action front-loaded. Each sentence adds a distinct operational or security fact, and there is no filler or repetition of schema content.

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 description sufficiently covers the call's purpose, operational role, and security implications while the schema carries parameter details. It mentions the result in terms of 'a fresh signed token and new expiry,' though it could more explicitly route the agent to status- or revoke-related siblings.

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 schema thoroughly documents lease_id and ttl_s including bounds, plus the deprecated vigil_key. The description adds no parameter-level detail beyond the schema, so the baseline score of 3 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 opens with a specific verb and resource: 'Extend a lease with a fresh signed token and new expiry.' It also distinguishes the operation from stopping, revoking, or granting by explaining that renewal is how a healthy agent keeps acting.

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?

It gives clear situational guidance: 'Renewing is how a healthy agent keeps acting; stop renewing (or revoke) and it lapses.' This tells the agent when renewal is appropriate, though it does not explicitly name sibling alternatives such as vigil_grant_lease or vigil_lease_status.

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

All Vigil — an outside witness for AI agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources