Cachly — AI Cognitive Brain

create_instance

Provision a new managed Valkey or Redis cache instance on the Cachly cloud platform, choosing from free or paid tiers. Free tier deploys in about 30 seconds; paid tiers return a Stripe checkout URL.

Instructions

Create a new managed Valkey/Redis cache instance on cachly.dev. Free tier provisions in ~30 seconds. Paid tiers return a Stripe checkout URL. Available tiers: free (25 MB), dev (200 MB, €19/mo), pro (900 MB, €49/mo), speed (900 MB Dragonfly + Semantic Cache, €79/mo), business (7 GB, €199/mo).

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>",
      "tier": "<tier>"
    },
    "name": "create_instance"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Unique name for the instance (min 3 chars)
`tier`	Yes	Pricing tier. Start with "free" for testing.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Apr 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses key behaviors: free tier provisions in ~30 seconds, paid tiers return a Stripe checkout URL. It also lists all available tiers with sizes and pricing. No annotations are provided, so the description carries the behavioral burden and handles it well.

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?

The description is concise: three sentences front-load the purpose and tier details, with no redundant or wasted language.

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?

Given the tool's simplicity (2 params, no output schema, no annotations), the description covers the creation process, tiers, and basic behavior. It could mention return values for free tier, but overall it's sufficiently complete.

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 schema has 100% coverage with descriptions for both parameters. The description adds value by explaining 'name' is unique and listing tier options with details not in the schema (e.g., 'Dragonfly + Semantic Cache' for speed tier).

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 clearly states the verb 'create' and the resource 'managed Valkey/Redis cache instance on cachly.dev'. It distinguishes from sibling tools like delete_instance, get_instance, and list_instances.

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?

The description explains when to use the tool (to create a cache instance) and mentions free vs paid tiers. While no explicit alternatives are given, the tool's purpose is distinct among siblings. The guidance on starting with 'free' tier is helpful.

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

Deploy Server