Skip to main content
Glama

List field values

malcolm_field_values
Read-only

List distinct values for a field with per-value document counts to see actual data before filtering.

Instructions

List a single field's distinct VALUES with per-value document counts.

    Use this to see what values a field actually holds before filtering on it, so
    you don't invent values. To confirm the field NAME exists first, use
    malcolm_field_search; to see which datasets carry the field, use
    malcolm_field_profile. For multi-field or nested bucketing, use
    malcolm_aggregate. A "-" in the output is Malcolm's placeholder for
    documents where the field is absent, not a value you can filter on.
    Returns a text list of "value (N docs)" lines.

    With no time range this reads only the last 24 hours, so a value that
    exists only in older data is missing here and reads as invalid —
    measured on Malcolm v26.07.1, network.protocol lists nothing at the
    default window while its top value carries millions of documents once
    time_from reaches the capture. Pass time_from before concluding a value
    is not in this Malcolm.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldYesField to enumerate distinct values for, e.g. "event.dataset" -> ["conn","dns","ssl",...]; "network.protocol" -> ["tcp","udp","icmp"]; "suricata.alert.severity" -> [1,2,3]. Confirm the name with malcolm_field_search.
limitNoMax distinct values to return, ordered by document count.
filtersNoOptional JSON filter (Malcolm filter syntax) scoping the enumeration. Empty = all documents.{}
time_toNoEnd time, dateparser format. Empty = now.
time_fromNoStart time, dateparser format. Empty = the last 24 hours, which holds nothing on a capture older than that.

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 openWorldHint=true, but the description adds substantial behavior: the output format as 'value (N docs)' lines, the '-' placeholder for absent fields, and the default last-24-hours window with a concrete Malcolm v26.07.1 example. This goes well beyond the structured annotations and is consistent with them.

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 front-loaded with purpose and usage in the first two sentences, then organized into clear caveats. The measured example about network.protocol is informative but makes the description slightly longer than strictly necessary. Overall, every sentence earns its place and the structure is logical.

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?

For a read-only enumeration tool with moderate complexity, the description covers purpose, when to use alternatives, output format, edge-case placeholder behavior, default time window, and a practical warning. Combined with the 100% schema coverage and presence of an output schema, the agent has a complete and unambiguous picture.

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?

The input schema already covers all 5 parameters at 100%, so the baseline is 3. The description adds value by explaining the '-' placeholder meaning, the default time-window consequence, and the need to pass time_from, which supplements the schema's brief parameter descriptions. It does not need to restate limit/filters since those are well documented in 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?

The description opens with 'List a single field's distinct VALUES with per-value document counts', which names a specific verb, resource, and unique output. It further distinguishes itself from siblings by explicitly naming malcolm_field_search, malcolm_field_profile, and malcolm_aggregate for different use cases.

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?

It explicitly states when to use the tool: 'Use this to see what values a field actually holds before filtering on it, so you don't invent values.' It names exact alternatives for other needs and provides a clear directive about the time window: 'Pass time_from before concluding a value is not in this Malcolm.'

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