Skip to main content
Glama
Sign In

OneLence

by com.onelence
OverviewDiscussionsAdmin

Checkout link

onelence_create_checkout_link
Read-onlyIdempotent

A OneLence billing link with the chosen plan highlighted. The user reviews and checks out in OneLence; nothing is charged from chat. Owners and admins only.

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": {
      "plan": "<plan>"
    },
    "name": "onelence_create_checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesPlan id from onelence_get_plans.
intervalNo

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
planYes
objectYes
intervalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "interval": {
+      "enum": [
+        "month",
+        "year"
+      ],
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "object": {
+      "const": "checkout_link",
+      "type": "string"
+    },
+    "plan": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "object",
+    "url",
+    "plan",
+    "interval",
+    "note"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured behavior: no charge occurs in chat, the actual transaction happens externally in OneLence, and access is gated to owners/admins. Missing are link lifetime/expiry and whether repeated calls produce the same URL, which would matter for an idempotent-flagged link generator.

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?

Two short sentences, with the artifact and the plan highlighting front-loaded, then the no-charge clarification and the role gate. No filler, but the leading noun phrase lacks a verb, making the action slightly less immediate than it could be.

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 values need not be explained, and annotations cover safety. Combined with the description's cost behavior and permission gate, an agent has nearly everything needed for a two-parameter tool; only link lifecycle details (expiry, reuse) are absent.

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 50%: 'plan' is documented (id from onelence_get_plans) and 'interval' carries an enum, so meaning is largely structured. The description only echoes 'the chosen plan' without explaining the interval parameter or the effect of omitting it, adding little beyond the schema — an appropriate baseline 3.

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 identifies the artifact produced — a OneLence billing link with the chosen plan highlighted — which lets an agent infer this generates a checkout URL for a selected plan. It is distinguishable from siblings like onelence_get_plans (which supplies the plan id) and from pricing/analytics tools, though the opening is a noun phrase rather than an explicit verb+resource, leaving the 'create' action implicit.

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?

The description supplies real context for when this applies: the user reviews and checks out inside OneLence, and nothing is charged from chat, plus an 'Owners and admins only' prerequisite. It does not, however, name any alternative or state what to do when the caller is not an owner/admin, so routing is implied rather than explicit.

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

All OneLence 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