Skip to main content
Glama

List saved Arkime value lists

arkime_shortcuts
Read-only

Lists Arkime's named value lists (IOC sets) with their contents, so you can reference existing lists in expressions.

Instructions

List Arkime's named value lists (IOC sets) and what each one contains.

    A shortcut is a named list of IPs, strings or numbers that an expression
    can reference as `$name` instead of spelling every value out. Use this
    before writing an expression so you reference a list that exists and
    know what is in it. For saved queries rather than value lists use
    arkime_views, for scheduled queries that stamp their own tags use
    arkime_crons, and to add a list of your own use arkime_create_shortcut
    (needs the arkime-view write class).

    Arkime scopes shortcuts by owner and role the same way it scopes views:
    its API filters the list by the requesting user and that user's roles,
    so this shows what the configured account can see, not everything on the
    server, and a name an expression then rejects as unknown may simply
    belong to someone else. That is Arkime's documented API behaviour rather
    than something measured here: Malcolm v26.07.1 ships no shortcut, so an
    empty list is the expected answer on a fresh deployment.
    Field meanings are in the output schema; use_in_expression is the token
    to paste, already spelled correctly.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax shortcuts to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds valuable behavioral context: scoping by the requesting user's roles, API-level filtering of visibility, and the expectation that a fresh deployment returns an empty list. This goes beyond the annotations to explain real-world behavior and a known pitfall.

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 a bit long but every sentence provides useful context. It is front-loaded with a clear one-line summary, followed by usage guidance, scoping behavior, and an explicit note about output schema fields. No filler is present.

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?

Given the tool's simplicity (1 optional parameter, no nested objects) and the presence of an output schema, the description is complete. It covers what the tool returns, user-scoping caveats, sibling tool distinctions, and a deployment-specific expectation. Nothing critical is missing.

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?

The schema covers the single 'limit' parameter 100%, so the description doesn't need to explain it. The description does not add parameter-specific meaning for the input; it focuses on output schema fields like 'use_in_expression' (which is output, not input). Thus, the baseline of 3 applies.

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 tool 'List Arkime's named value lists (IOC sets) and what each one contains.' It uses a specific verb (list) and resource (value lists), immediately distinguishing it from sibling tools by mentioning arkime_views, arkime_crons, and arkime_create_shortcut.

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?

The description gives explicit when-to-use guidance: 'Use this before writing an expression so you reference a list that exists and know what is in it.' It also names alternatives (arkime_views for saved queries, arkime_crons for scheduled queries, arkime_create_shortcut for adding lists) and notes the permission requirement for creating lists.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nagameTW/mcp-server-malcolm'

If you have feedback or need assistance with the MCP directory API, please join our Discord server