Skip to main content
Glama

Start a license for a virtual space or apartment

start_space_license

Places a license request for one unit and term, for the person or business you act for, and returns the request number, the total and a Stripe checkout link for the licensee to pay by card. Nothing is charged until it is paid. The order is governed by the AREMES Space License (https://aremes-enterprises.com/lease/license/) and is accepted only when agree is true, meaning the licensee has agreed to it.

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": {
      "name": "<name>",
      "email": "<email>",
      "unit": "<unit>",
      "term": "<term>",
      "agree": "<agree>"
    },
    "name": "start_space_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe licensee's full name.
termYes1m = one month; 6m-up = six months paid in full (10% off); 1y-up = one year paid in full (20% off).
unitYesUnit id, e.g. "A", "C-204", "R-101", "PH-A".
agreeYesTrue only if the licensee read and agreed to the AREMES Space License.
emailYesThe licensee's e-mail address.
notesNoOptional notes for the artist.
startNoOptional start date, YYYY-MM-DD.
businessNoOptional business name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare the generic mutation profile (readOnly=false, destructive=false, idempotent=false). The description adds real behavior: nothing is charged until payment, the request number/total/checkout link are returned, and acceptance is gated on agree=true. It does not warn that repeat calls create separate requests despite idempotentHint=false, which is the one notable gap.

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 sentences, front-loaded with the action and the return value, then the payment behavior, then the acceptance gate. No filler; the legal URL and agree condition each carry decision-relevant weight.

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 an 8-parameter mutation with no output schema, the description covers what is created, what is returned, the payment flow, and the blocking condition. Remaining gaps are minor — defaulting of the optional start date and the business field's effect on the request — and are partly covered by the schema.

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 coverage is 100%, so the schema already documents every parameter including the term enum and unit id format. The description reinforces the agree semantics ("meaning the licensee has agreed to it") and the unit+term pairing but adds no syntax or constraints beyond the schema, so baseline 3 applies.

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?

"Places a license request for one unit and term" is a specific verb+resource, and the description immediately names the return payload (request number, total, Stripe checkout link). It is clearly a space/apartment licensing tool distinct from the image/model license siblings, though it never names those alternatives to sharpen the boundary.

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?

Usage is implied by the unit/term framing and the "agree must be true" condition, which tells the agent a prerequisite. However, there is no explicit when-to-use-this-vs-start_image_license or start_model_license guidance, and no stated exclusions or preconditions beyond the license agreement.

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