Skip to main content
Glama

MCP OAuth client-interop conformance

Subscribe (Solo or Fleet)

subscribe_solo

activate/extend a subscription via x402 X-PAYMENT header (the POST /subscribe operation; Bearer token required): Solo $9/mo per server by default, or Fleet $29/mo for up to 10 servers with tier=fleet (WO-F-P22-17/RT-20 — the tier parameter is advertised here exactly as in the REST OpenAPI). The embedded check shape (server_config / idp_shape / full_matrix / clients / apply_shims / check) is accepted and stored for hourly re-runs, exactly as REST.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "subscribe_solo"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNo
checkNo
clientsNo
serversNo
idp_shapeNo
apply_shimsNo
full_matrixNo
server_nameNo
server_configNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / apply_shims
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / check
      Added value: +{
      +  "type": "object"
      +}
    • addedInput schema / properties / clients
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / full_matrix
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / idp_shape
      Added value: +{
      +  "enum": [
      +    "dcr_friendly",
      +    "cognito_like",
      +    "strict_loopback"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / server_config
      Added value: +{
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / servers
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / tier
      Added value: +{
      +  "enum": [
      +    "solo",
      +    "fleet"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false/destructiveHint=false; the description goes further by disclosing that a Bearer token is required and that payment is carried in an x402 X-PAYMENT header, plus concrete prices — essential context for a paid mutation. It omits what happens on payment failure, whether re-calling extends vs. duplicates a subscription, and what the response contains.

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 purpose and pricing are front-loaded, which is good, but the single run-on sentence is cluttered with internal references ("WO-F-P22-17/RT-20") and meta-commentary ("advertised here exactly as in the REST OpenAPI", "exactly as REST") that add no decision value for an agent.

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

Completeness3/5

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

For a 9-parameter, nested-object, mutating tool with no output schema, the description covers auth, payment, pricing, and most of the check payload. It still leaves two parameters undocumented and says nothing about the returned subscription object or how extension is handled, which matters for a paid write operation.

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?

With 0% schema description coverage the description must carry the load, and it does name most fields — tier, check, server_config, idp_shape, full_matrix, clients, apply_shims — and explains that the check payload is "stored for hourly re-runs". However servers and server_name go unmentioned, and the named fields get no value semantics beyond the enum names, so compensation is partial.

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?

States a specific verb and resource: "activate/extend a subscription via x402 X-PAYMENT header (the POST /subscribe operation)", and adds the two pricing modes (Solo $9/mo per server, Fleet $29/mo up to 10 servers). It does not name or differentiate against any sibling (claim_trial, subscription_status), so the agent must infer the boundary itself.

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 indicates the trigger (activate or extend a paid subscription) and the tier selection rule ("tier=fleet" for Fleet, solo by default). It never says when to prefer claim_trial instead, nor that subscription_status should be used to check state rather than subscribing, leaving the sibling routing implicit.

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