Skip to main content
Glama

Liminal

by ai.physea
OverviewDiscussionsAdmin

read

Your saved results and sources. kind: work|results|sources; query filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo
queryNo
contextYesDescribe the user's goal in one short sentence. Omit personal data and secrets.
llm_modelYesThe 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. Changed7 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"
+}
    • removedInput schema / properties / kind / default
      Removed value: -""
    • removedInput schema / properties / kind / title
      Removed value: -"Kind"
    • removedInput schema / properties / query / default
      Removed value: -""
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • addedInput schema / required
      Added value: +[
+  "context"
+]
    • removedInput schema / title
      Removed value: -"read_toolArguments"
  3. First observed

TDQS

C2.6/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 behavioral burden, yet it discloses almost nothing: no read-only confirmation, no pagination or result-size behavior, no return format. 'query filters' is the only behavioral hint, which is far short of what an unannotated tool needs.

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?

The definition is a single compact, front-loaded fragment pair with no wasted words. It is terse to the point of under-specification, but structurally there is nothing extraneous to trim.

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

Completeness2/5

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

With 4 params (two of them unusual required metadata fields), no output schema, and no annotations, the description should explain what is returned and how results are shaped, but it does not. For a tool whose name gives no clue and whose required params are non-obvious, this leaves significant gaps.

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 50%: the two required params (context, llm_model) are documented in the schema, while kind and query are not. The description partially compensates by enumerating kind values (work|results|sources) and noting that query filters, but 'query filters' is too vague to fully explain the parameter's syntax or matching behavior.

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

Purpose3/5

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

The noun phrase 'Your saved results and sources' implies retrieval and the 'kind: work|results|sources' fragment hints at the resource scope, but the description never states a verb and does not distinguish this generic 'read' tool from siblings like research, focus, or solve. An agent can guess it retrieves saved artifacts, but the purpose is only loosely pinned down.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool. The only routing signal is the implied 'kind' selector, which is left for the agent to infer.

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

All Liminal toolsInspect
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.

Resources