Skip to main content
Glama

Search index fields

malcolm_field_search
Read-only

Discover which field names exist in Malcolm's index by keyword, prefix, or type. Confirms exact spellings before querying and returns a sorted list of name (type).

Instructions

Discover which field NAMES exist in Malcolm's index, by keyword, prefix, or type.

    Use this first, before any query, to confirm a field name exists — Malcolm uses
    non-standard names (e.g. http.useragent, NOT http.user_agent). To then see the
    VALUES a field holds, use malcolm_field_values; to see which datasets contain
    it, use malcolm_field_profile. Do NOT source an arkime_* argument from here:
    these are the names malcolm_* and search_dsl take, and Arkime has its own
    spelling for the same field (ip.src, srcIp) that arkime_field_search reports.
    Pass at least one argument. Returns a text list of "name (type)" lines,
    sorted alphabetically.

    Arguments narrow (AND), they never widen, and the mapping is big enough
    that one keyword rarely lands: it runs to thousands of fields, and a
    keyword as common as "ip" matches over a thousand of them on its own.
    The header line counts every match but only the first 100 names are
    printed, so add a prefix or a field_type rather than reading the printed
    list as the whole answer.
    

Input Schema

NameRequiredDescriptionDefault
prefixNoField-name prefix to match, e.g. "zeek.dns", "suricata.alert", "rule". Empty = no prefix filter.
keywordNoSubstring to match anywhere in a field name, e.g. "useragent", "signature". Empty = no keyword filter.
field_typeNoFilter by the type Malcolm reports for a field — those are "string", "integer", "float", "date", "ip" and "geo". They are NOT OpenSearch type names: "keyword", "long" and "text" match nothing here, even though index_mapping reports the same fields under those names. Empty = any type.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.1
    • changedInput schema / properties / field_type / description
      Previous value: -"Filter by the type Malcolm reports for a field — measured on Malcolm v26.07.1 those are \"string\", \"integer\", \"float\", \"date\", \"ip\" and \"geo\". They are NOT OpenSearch type names: \"keyword\", \"long\" and \"text\" match nothing here, even though index_mapping reports the same fields under those names. Empty = any type."New value: +"Filter by the type Malcolm reports for a field — those are \"string\", \"integer\", \"float\", \"date\", \"ip\" and \"geo\". They are NOT OpenSearch type names: \"keyword\", \"long\" and \"text\" match nothing here, even though index_mapping reports the same fields under those names. Empty = any type."
  2. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / field_type / description
      Previous value: -"Filter by OpenSearch field type, e.g. \"keyword\", \"ip\", \"long\", \"date\". Empty = any type."New value: +"Filter by the type Malcolm reports for a field — measured on Malcolm v26.07.1 those are \"string\", \"integer\", \"float\", \"date\", \"ip\" and \"geo\". They are NOT OpenSearch type names: \"keyword\", \"long\" and \"text\" match nothing here, even though index_mapping reports the same fields under those names. Empty = any type."
  3. Addedv0.3.2
  4. Removedv0.3.0
  5. 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 only cover read-only safety, so the description adds substantial behavioral context: arguments narrow (AND) never widen, one keyword rarely lands, the mapping runs to thousands of fields, and only the first 100 names are printed while the header counts all matches. That is exactly the operational caveat an agent needs to avoid misreading results.

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 purpose, then alternatives, then caveats in a logical order. Every sentence earns its place, though the warning about keyword breadth and the 100-item limit is slightly repetitive and could be tightened.

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?

Complete for a search tool with full schema coverage, a return-shape note ('text list of "name (type)" lines, sorted alphabetically'), and annotations covering safety. An agent has everything needed to call it correctly and interpret the output.

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%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining that filters AND together, that a common keyword matches over a thousand fields, and that a prefix or field_type should be used instead of trusting the printed list. It does not restate parameter definitions, which is correct given 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+resource ('Discover which field NAMES exist in Malcolm's index') and scopes it by keyword, prefix, or type. It distinguishes itself from siblings malcolm_field_values, malcolm_field_profile, and arkime_field_search explicitly.

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 says 'Use this first, before any query' and routes to alternatives: malcolm_field_values for values, malcolm_field_profile for datasets, arkime_field_search for arkime_* spellings. It also gives an exclusion ('Do NOT source an arkime_* argument from here') and a constraint ('Pass at least one argument').

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