Skip to main content
Glama
nagameTW

mcp-server-malcolm

by nagameTW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Look up one session by id

arkime_session_detail
Read-only

Fetch the full stored Arkime session document by id, returning @timestamp, tags, event block, and Zeek/Suricata detail omitted from session rows.

Instructions

Fetch the session Arkime holds under one id — a point lookup, not a search.

    What comes back is the full stored document for that session, including
    @timestamp, `tags`, the `event` block and the Zeek / Suricata detail
    that arkime_sessions rows leave out. For the session's raw packets use
    arkime_session_pcap; for what the two sides actually sent, the payload
    bytes rather than parsed fields, use arkime_session_payload; for
    distinct values across many sessions use arkime_unique /
    arkime_spiview.

    An id this deployment does not hold is answered with a sentence rather
    than an error, so a bare "no session found" means the id aged out of
    retention or came from somewhere other than arkime_sessions — ids are
    not stable across re-indexing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesOne Arkime session id from arkime_sessions results (arkime_sessions is the only source of these ids).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0
  2. Removedv0.2.0
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/safe semantics, but the description adds real behavioral context beyond them: the returned document is the full stored form including fields arkime_sessions rows omit, a missing id returns a sentence rather than an error, and ids are not stable across re-indexing. These are exactly the traits an agent needs before trusting a lookup.

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?

Front-loaded with the core action and the search contrast in the first sentence, then alternatives, then failure mode. Slightly prose-heavy and longer than strictly necessary, but every sentence carries information the agent needs.

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

Completeness5/5

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

Output schema exists so return values need no explanation, yet the description still characterizes what the document contains and how failures surface. For a one-parameter read tool with full annotation coverage, nothing needed for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter is already documented as coming from arkime_sessions results. The description reinforces the id's provenance and adds the non-obvious caveat that ids are not stable across re-indexing, which is genuine semantic value beyond the schema.

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?

States a specific verb and resource ('Fetch the session Arkime holds under one id') and immediately differentiates the operation from search with 'a point lookup, not a search.' An agent can distinguish it from arkime_sessions without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes to three alternatives with the condition that selects each: arkime_session_pcap for raw packets, arkime_session_payload for payload bytes vs parsed fields, arkime_unique/arkime_spiview for distinct values across many sessions. Also explains the not-found case, which is the main usage ambiguity for a lookup tool.

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