Skip to main content
Glama

Liminal

read

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

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": "read"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
queryNo
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. 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"
  5. First observed

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it never states that this is a read-only retrieval, whether results are paginated or truncated, how many items return, or what access is required. For a tool with zero annotation coverage, this leaves the agent guessing about side effects and response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short fragments, front-loaded and free of filler, which is good. The telegraphic style ("query filters.") is under-specified rather than concise, so brevity comes at the cost of clarity.

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 four parameters, no annotations, and no output schema, the description must explain both behavior and return values. It supplies neither, so an agent cannot tell what a call returns or how the kind values change the result set.

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%: context and llm_model are documented in-schema while kind and query are bare strings. The description partially compensates by enumerating kind values (work|results|sources) that the schema does not express as an enum, and by saying query filters, but it never explains query syntax or whether kind is required.

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?

"Your saved results and sources" identifies the resource (previously saved results/sources) and the kind values narrow it to work|results|sources, so an agent can infer this retrieves stored items. However, there is no verb at all and nothing distinguishes it from siblings like search, fetch, or research, leaving the exact operation implicit.

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 statement of when to use this tool versus search, fetch, or research, and no prerequisites or exclusions. The only implied guidance is that it concerns already-saved material, which an agent must infer from the noun phrase.

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.