Liminal

solve

Frame and answer a non-trivial decision or multi-step request in one call; skip simple lookups. More args: get_capabilities(tool=...).

Input Schema

TableJSON Schema

Name	Required	Description
`context`	No
`task_id`	No
`question`	Yes	the complete request
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`follow_up_of`	No	result_id this continues

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "question"
-]New value: +[
+  "question",
+  "llm_model"
+]

Changed20 schema fields changedOct 18, 2026

removedInput schema / properties / checkpoint_id

Removed value: -{
-  "default": "",
-  "title": "Checkpoint Id",
-  "type": "string"
-}

removedInput schema / properties / context / default
```
Removed value: -""
```
removedInput schema / properties / context / title
```
Removed value: -"Context"
```

removedInput schema / properties / context_brief_id

Removed value: -{
-  "default": "",
-  "title": "Context Brief Id",
-  "type": "string"
-}

removedInput schema / properties / depth

Removed value: -{
-  "anyOf": [
-    {
-      "enum": [
-        "shallow",
-        "standard",
-        "deep"
-      ],
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Depth"
-}

removedInput schema / properties / follow_up_of / default
```
Removed value: -""
```
addedInput schema / properties / follow_up_of / description
```
Added value: +"result_id this continues"
```
removedInput schema / properties / follow_up_of / title
```
Removed value: -"Follow Up Of"
```

removedInput schema / properties / max_reduction_depth

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Max Reduction Depth"
-}

removedInput schema / properties / preference_policy

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Preference Policy"
-}

addedInput schema / properties / question / description
```
Added value: +"the complete request"
```
removedInput schema / properties / question / title
```
Removed value: -"Question"
```

removedInput schema / properties / resources

Removed value: -{
-  "default": "",
-  "title": "Resources",
-  "type": "string"
-}

removedInput schema / properties / task_id / default
```
Removed value: -""
```
removedInput schema / properties / task_id / title
```
Removed value: -"Task Id"
```

removedInput schema / properties / tool_manifest

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Tool Manifest"
-}

removedInput schema / properties / trace

Removed value: -{
-  "anyOf": [
-    {
-      "enum": [
-        "off",
-        "summary",
-        "verbose"
-      ],
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Trace"
-}

removedInput schema / properties / user_id

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "User Id"
-}

removedInput schema / properties / verbose

Removed value: -{
-  "default": false,
-  "title": "Verbose",
-  "type": "boolean"
-}

removedInput schema / title
```
Removed value: -"solveArguments"
```

First observedOct 12, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It hints at single-call batching ('in one call') but says nothing about cost, latency, side effects, whether the operation is read-only, or what a result looks like — significant gaps for a tool that performs reasoning over a request.

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?

A single compact sentence with the core purpose front-loaded and the exclusion clause immediately after. Every clause carries information, though the trailing get_capabilities pointer is somewhat abrupt.

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?

With five parameters, no annotations, and no output schema, the description is thin — it never explains what 'frame' produces or what a caller gets back. It leans on the get_capabilities escape hatch, which is helpful but not a substitute for describing the tool's own behavior.

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 60%: question and llm_model are well documented in the schema, follow_up_of has a terse description, while context and task_id are undocumented. The description adds only a pointer to get_capabilities for the remaining args rather than explaining any parameter itself.

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 concrete verb+resource ('frame and answer a non-trivial decision or multi-step request') and scopes it against simple work ('skip simple lookups'). However, it does not differentiate itself from sibling tools like research or focus, which an agent might reasonably confuse for the same multi-step reasoning task.

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?

Gives a clear when-not condition ('skip simple lookups') and routes the agent to get_capabilities(tool=...) for additional arguments. It stops short of naming the concrete alternatives (research, focus, read) that would fully resolve selection ambiguity.

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

All Liminal tools Inspect

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.