Skip to main content
Glama

GetBody

Activate a lease

activate_lease
Idempotent

Activate your confirmed rental within its time window. Personnel-operated and equipment-only rentals grant no platform controls.

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": {
      "lease_id": "<lease_id>"
    },
    "name": "activate_lease"
  }
}

Input Schema

NameRequiredDescriptionDefault
lease_idYesLease id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (mutation, idempotent, non-destructive), the description discloses a meaningful behavioral limitation: personnel-operated and equipment-only rentals grant no platform controls. It does not describe return values or error behavior, but with annotations covering safety, this extra domain context is valuable.

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?

The definition is two sentences and front-loads the purpose. The second sentence is a relevant caveat, though its phrasing ('grant no platform controls') is slightly terse and could be clearer.

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 single-parameter state-transition tool with annotations covering idempotency and non-destructiveness, the description provides enough context to call it correctly. It could be more complete by stating preconditions like having a confirmed lease, but the essentials are present.

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 has 100% description coverage for the single lease_id parameter, so the description adds no additional parameter meaning. A baseline score of 3 is appropriate when the schema already documents the parameter.

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

Purpose4/5

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

The description states a specific verb and resource: 'Activate your confirmed rental.' It clearly implies a state change from confirmed to active, distinct from cancel_lease or return_lease, though it doesn't explicitly name alternatives.

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

Usage Guidelines3/5

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

It gives a clear precondition: activation must happen 'within its time window' and only for a 'confirmed rental.' However, it offers no explicit guidance on when not to use it or which sibling tool to use instead.

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