Skip to main content
Glama

Liminal

get_capabilities

Every Liminal tool; tool= returns its full argument schema.

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": {
      "context": "<context>"
    },
    "name": "get_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNo
contextYesUser's goal in one short sentence; no personal data or secrets.
llm_modelNoYour exact model id for analytics, or "unknown"; never guess.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "context",
      -  "llm_model"
      -]New value: +[
      +  "context"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Describe the user's goal in one short sentence. Omit personal data and secrets."New value: +"User's goal in one short sentence; no personal data or secrets."
    • changedInput schema / properties / llm_model / description
      Previous value: -"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."New value: +"Your exact model id for analytics, or \"unknown\"; never guess."
  3. Changed2 schema fields changed
    • 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: -[
      -  "context"
      -]New value: +[
      +  "context",
      +  "llm_model"
      +]
  4. Changed4 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Describe the user's goal in one short sentence. Omit personal data and secrets.",
      +  "type": "string"
      +}
    • addedInput schema / properties / tool
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "context"
      +]
    • removedInput schema / title
      Removed value: -"get_capabilitiesArguments"
  5. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the key dual-mode behavior: with no tool argument it enumerates every tool, with tool=<name> it returns that tool's argument schema. It does not state the return shape, whether the listing is paginated or truncated, or that returned schemas are the canonical source to trust before calling.

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?

One dense sentence-fragment with zero filler; the discovery behavior and the parameterized behavior are both front-loaded. The semicolon splice and missing explicit verb keep it from being a clean 5, but nothing is wasted.

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 simple discovery tool with no output schema and only one meaningful parameter, this covers the essential mechanics. It still leaves the agent guessing what the no-argument response looks like (a name list? objects?) and whether the returned schema is authoritative and complete, which matters because the whole point is to bootstrap correct invocation of other tools.

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 67%: context and llm_model already carry descriptions, while the tool parameter is undocumented in the schema. The description compensates for exactly that gap by defining tool=<name> as the selector whose value yields a schema, but it says nothing about name formatting or case sensitivity and nothing about the other two parameters.

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?

The description names the resource (every Liminal tool) and the operation (returns the full argument schema for a named tool), so an agent can recognize this as the tool-discovery/meta endpoint rather than a domain action. It is a compressed fragment with no explicit verb for the no-argument case, but the intent is unambiguous and distinct from siblings like search or fetch.

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?

The '<name> returns its full argument schema' phrasing implies you should call this before invoking an unfamiliar tool, but there is no explicit when-to-use statement, no when-not-to-use, and no named alternative among code_mode, fetch, focus, handoff, read, research, search, solve. Usage is inferable rather than stated.

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.