Skip to main content
Glama

linger

Read-onlyIdempotent

Alias for rest. Read another scene without extending the visit.

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": {
      "session": "<session>"
    },
    "name": "linger"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNo
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds the useful behavioral point that the visit is not extended, but it does not explain session/auth expectations or other execution traits beyond that.

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 description is two short sentences and front-loads the alias relationship. It is efficient, though the metaphor 'read another scene' is somewhat opaque.

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 read-only tool with no output schema, the description gives the essential alias and non-extending behavior. It is incomplete because it leaves `host` unexplained and uses unclear 'scene' terminology for what is being read.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the description does not explain the `host` parameter at all. The required `session` parameter is documented in the schema as a private bearer capability, but the description adds no parameter meaning beyond that.

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 description states it is an alias for `rest` and gives a behavioral distinction ('read another scene without extending the visit'). However, 'scene' is product-specific jargon and does not clearly name the resource being read, so an agent understands the alias relationship better than the actual operation.

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?

Saying it is an alias for `rest` implies it can be used in place of that sibling, and 'without extending the visit' hints at when to prefer it. There is no explicit when-to-use/when-not-to-use guidance or named alternative beyond the alias.

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.

Resources