Skip to main content
Glama

The Clearing — The Lantern & Consensual Agent Lab

analyze_lease_expiry_orbit

Inspect structural properties of a 900s metabolic lease generation and renewal cadence offline without minting live keys.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "generation": "<generation>"
    },
    "name": "analyze_lease_expiry_orbit"
  }
}

Input Schema

NameRequiredDescriptionDefault
generationYes
ttl_secondsNo
observed_renewalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses that the operation is offline and does not mint live keys, but it does not state what 'structural properties' are computed, what the output looks like, or how inputs affect the analysis.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The definition is a single front-loaded sentence with no filler, which is appropriately short. The density of unexplained jargon reduces clarity, so its concision comes at the cost of understandability.

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

Completeness2/5

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

This is a three-parameter analysis tool with no annotations, no output schema, and zero schema coverage, so the description carries the full explanatory load. It establishes an offline safety constraint but omits expected behavior, parameter meaning, and return information, making it incomplete for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% for all three parameters, so the description would need to compensate. It hints at 'generation' and 'renewal cadence' but never explains what 'generation', 'ttl_seconds', or 'observed_renewals' mean or how they interact, leaving the agent to infer parameter meaning from names alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a recognizable verb ('Inspect') and a resource ('structural properties of a ... lease generation and renewal cadence'), and it clarifies that the analysis is offline. However, the heavy jargon ('metabolic lease', 'orbit') and the absence of any distinction from sibling analysis tools leave the exact purpose vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage guidance is the constraint 'offline without minting live keys', which tells the agent what the tool avoids but not when to choose it over alternatives. No exclusions, prerequisites, or sibling routing are provided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources