Tomorrow Lives Engines

Read the plan

subscription

Read-onlyIdempotent

The account's plan: a pass (its window of included units, when access ends, and that it never renews) or a person's card plan (its period and renewal), the owner's state, what is paid, and pass_quote: what the next pass costs this account. An agent buys a 30-day pass with a shared payment token: $1.00 the first time (a one-time offer for a new owner), then $20.00, with 1,500 units each. A pass never renews. Buying is a REST call with a payment token, not a tool: POST /api/agents/subscribe for a pass, POST /api/agents/units for a unit pack. Costs nothing.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`pass_quote`	No	What the next pass costs this account, and why.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "pass_quote": {
+      "description": "What the next pass costs this account, and why."
+    }
+  },
+  "type": "object"
+}

First observedOct 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), so the bar is low. The description still adds real context beyond them: the call costs nothing, a pass never renews, pricing tiers ($1.00 one-time, then $20.00 with 1,500 units), and that purchasing requires a shared payment token over REST.

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

Conciseness2/5

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

Roughly 110 words for a zero-parameter read tool. It repeats the same fact twice ('that it never renews' and again 'A pass never renews') and devotes several sentences to pricing and purchase endpoints that this tool does not perform, padding a description whose actual job is one sentence.

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?

An output schema exists, so return-value explanation is not required, yet the description still glosses the field meanings. Five of the six fields plus pricing context are addressed; only the practical read workflow is left implicit.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description adds nothing parameter-related, and there is nothing to add.

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 resource (the account's plan) and enumerates what it returns: a pass with its unit window and end date, a card plan with period and renewal, owner state, amount paid, and pass_quote. It does not differentiate itself from any sibling tool, so it stays at 4 rather than 5.

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 explicitly warns that buying is a REST call with a payment token and not this tool, naming POST /api/agents/subscribe and POST /api/agents/units as the alternatives. That is genuine when-not guidance, though it never states plainly when an agent should call this read tool instead of, say, usage or owner.

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

All Tomorrow Lives Engines tools Inspect

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

Need Help?