Skip to main content
Glama
Sign In
ltm

ltm

by dennisdevulder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

ls

List recent session packets from the ltm server, returning ID, creation time, and goal for each. Optionally set a maximum number of packets to retrieve.

Instructions

List recent packets on the configured ltm server. Returns a table with ID, creation time, and goal.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ls"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of packets to return (default 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description must fully disclose behavior. It only states the action and output, omitting important details like whether the operation is read-only, any prerequisites, permission requirements, or how 'recent' is defined. This lack of behavioral context weakens transparency.

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

Conciseness5/5

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

The description is concise with two sentences, free of extraneous information. Every sentence serves a clear purpose: stating the action and the output structure.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description covers the basic purpose and output. However, it lacks usage context and behavioral details that would make it fully self-contained. The output schema absence is partially mitigated by describing the returned fields.

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 100% (one parameter 'limit' with description). The tool description adds no additional parameter semantics beyond the schema. Baseline score of 3 is appropriate as the schema already documents the parameter adequately.

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

Purpose5/5

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

The description clearly states the verb 'list', the resource 'recent packets', the server 'ltm', and the output format 'table with ID, creation time, and goal'. It effectively distinguishes from sibling tools like 'push' or 'pull' which perform different operations.

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?

The description provides no guidance on when to use this tool versus its siblings. No when-to-use or when-not-to-use context is provided, leaving the agent without decision support for tool selection.

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

Deploy Server

Other Tools