CraveUp MCP Server

Official

by craveup-oss

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

List Crave Up subscription plans

list_subscription_plans

Read-onlyIdempotent

List available subscription plans with pricing, billing intervals, and trial periods. Use returned priceId to start a subscription checkout.

Instructions

List available subscription plans (name, price, billing interval, trial). Use the priceId with start_subscription_checkout. Production only; sandbox development does not require a subscription. Requires craveup login.

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": "list_subscription_plans"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	No
`mode`	Yes
`status`	Yes
`changes`	Yes
`summary`	Yes
`operation`	Yes
`planDigest`	Yes
`environment`	Yes
`nextActions`	Yes
`schemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.1Aug 31, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond those annotations by specifying the production-only constraint and the requirement for a craveup login, which are not captured in the structured annotations.

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 short sentences with no filler. The action and key fields come first, followed by downstream routing and environment requirements, so the most decision-relevant information is front-loaded.

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

Completeness5/5

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

With zero parameters, an output schema present, and annotations covering the safety profile, the description provides everything needed to call and use the tool correctly: login requirement, environment constraint, returned fields, and downstream integration.

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 has zero parameters, so the baseline is 4. The description adds value by listing the output fields (name, price, billing interval, trial) and explaining how the resulting priceId is used, which helps an agent interpret the tool's response without any input schema.

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

Purpose5/5

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

The description uses a specific verb and resource ('List available subscription plans') and names the key fields (name, price, billing interval, trial), making the tool's purpose unmistakable. It also differentiates itself from start_subscription_checkout by explicitly pointing to the priceId relationship.

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

Usage Guidelines5/5

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

It clearly states when the tool is needed: production use, while sandbox development does not require a subscription. It also names the downstream tool to use with the returned priceId, giving an agent concrete routing guidance.

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