Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

cache_get

Get a value from a running cache instance by key. Returns the stored value (string or deserialized JSON object) or null if the key does not exist or has expired. Read-only — no side effects. Use cache_mget when you need multiple keys in one round-trip. Use cache_exists to check existence without retrieving the value. Use semantic_search when you need fuzzy/vector search across stored values.

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": {
      "key": "<key>"
    },
    "name": "cache_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesCache key to retrieve
org_idNoOptional org ID — if the direct key misses, falls back to the shared org namespace org:{org_id}:sem:{key}
instance_idNoUUID of the instance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does most of the work: it declares read-only with no side effects and explains the miss semantics (null when the key does not exist or has expired). It stops short of operational context such as authentication requirements, TTL details, or consistency/latency characteristics, which keeps it from a 5.

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?

Front-loaded with the core action and return contract, then three tight routing sentences. Every sentence either discloses behavior or directs the agent to a different tool; there is no filler.

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?

For a three-parameter read tool with no output schema, the description covers what is missing structurally: it explains the return shape and the null/expired case, plus full sibling routing. Nothing an agent needs in order to call this correctly is 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 100%, so all three parameters — including the org_id fallback into the org:{org_id}:sem:{key} namespace and the instance UUID — are already documented in structured data. The description adds only the return-type note (string or deserialized JSON object), not parameter meaning, so the baseline of 3 applies.

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?

States a specific verb and resource ("Get a value from a running cache instance by key") and immediately scopes it against named siblings. An agent can distinguish it from cache_mget, cache_exists, and semantic_search without opening any schema.

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?

Explicitly names three alternatives and the condition that selects each: cache_mget for multiple keys in one round-trip, cache_exists for existence checks without retrieval, semantic_search for fuzzy/vector lookup. This is exactly the when-to-use-vs-alternative guidance the dimension rewards.

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.