Skip to main content
Glama

List ISM controls

list_controls

Retrieve a filtered list of ISM controls by applicability, group name, or label prefix. Paginate to navigate results.

Instructions

Returns a paginated, filtered list of ISM controls. Supports filters by applicability, group/section name (substring), and label prefix (e.g. "GOV", "AC", "PHYS").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
versionNo
applicabilityNoApplicability marking: NC=Non-classified, OS=OFFICIAL: Sensitive, P=PROTECTED, S=SECRET, TS=TOP SECRET.
groupNoSubstring match against group/chapter titles.
labelPrefixNoMatch controls whose label starts with this prefix, e.g. "GOV".
limitNo
offsetNo

Implementation Reference

  • Handler function for list_controls tool: resolves version, loads flat controls, applies filters via searchControls, maps results through compactControl, and returns paginated output.
    async ({ version, applicability, group, labelPrefix, limit, offset }) => {
      const v = await resolveVersion(version);
      const flat = await loadFlat(v.tag);
      const result = searchControls(flat, {
        applicability: applicability as Applicability | undefined,
        group,
        labelPrefix,
        limit,
        offset,
      });
      return txt({
        version: v.id,
        total: result.total,
        returned: result.items.length,
        offset: offset ?? 0,
        items: result.items.map(compactControl),
      });
    },
  • Input schema for list_controls tool: optional version, applicability (enum), group substring, labelPrefix, limit (1-500), and offset.
    inputSchema: {
      version: z.string().optional(),
      applicability: ApplicabilitySchema.optional(),
      group: z
        .string()
        .optional()
        .describe("Substring match against group/chapter titles."),
      labelPrefix: z
        .string()
        .optional()
        .describe(
          'Match controls whose label starts with this prefix, e.g. "GOV".',
        ),
      limit: z.number().int().min(1).max(500).optional(),
      offset: z.number().int().min(0).optional(),
    },
  • Applicability enum schema (NC, OS, P, S, TS) used by list_controls input schema.
    const ApplicabilitySchema = z
      .enum(["NC", "OS", "P", "S", "TS"])
      .describe(
        "Applicability marking: NC=Non-classified, OS=OFFICIAL: Sensitive, P=PROTECTED, S=SECRET, TS=TOP SECRET.",
      );
  • src/index.ts:205-246 (registration)
    Registration of the list_controls tool via server.registerTool with its name, metadata, schema, and handler.
    server.registerTool(
      "list_controls",
      {
        title: "List ISM controls",
        description:
          'Returns a paginated, filtered list of ISM controls. Supports filters by applicability, group/section name (substring), and label prefix (e.g. "GOV", "AC", "PHYS").',
        inputSchema: {
          version: z.string().optional(),
          applicability: ApplicabilitySchema.optional(),
          group: z
            .string()
            .optional()
            .describe("Substring match against group/chapter titles."),
          labelPrefix: z
            .string()
            .optional()
            .describe(
              'Match controls whose label starts with this prefix, e.g. "GOV".',
            ),
          limit: z.number().int().min(1).max(500).optional(),
          offset: z.number().int().min(0).optional(),
        },
      },
      async ({ version, applicability, group, labelPrefix, limit, offset }) => {
        const v = await resolveVersion(version);
        const flat = await loadFlat(v.tag);
        const result = searchControls(flat, {
          applicability: applicability as Applicability | undefined,
          group,
          labelPrefix,
          limit,
          offset,
        });
        return txt({
          version: v.id,
          total: result.total,
          returned: result.items.length,
          offset: offset ?? 0,
          items: result.items.map(compactControl),
        });
      },
    );
  • searchControls function: filters FlatControl array by applicability, group substring, labelPrefix, and supports pagination with limit/offset. Called by the list_controls handler.
    export function searchControls(
      controls: FlatControl[],
      opts: SearchOptions,
    ): SearchResult {
      const q = opts.query?.toLowerCase().trim();
      const groupQ = opts.group?.toLowerCase().trim();
      const labelPrefix = opts.labelPrefix?.toUpperCase().trim();
    
      const filtered = controls.filter((c) => {
        if (opts.applicability && !c.applicability.includes(opts.applicability))
          return false;
        if (groupQ && !c.groupPath.some((g) => g.toLowerCase().includes(groupQ)))
          return false;
        if (labelPrefix && !c.label.toUpperCase().startsWith(labelPrefix))
          return false;
        if (q) {
          const hay =
            `${c.label} ${c.title} ${c.statement} ${c.groupPath.join(" ")}`.toLowerCase();
          if (!hay.includes(q)) return false;
        }
        return true;
      });
    
      const offset = Math.max(0, opts.offset ?? 0);
      const limit = Math.max(1, Math.min(opts.limit ?? 50, 500));
      return {
        total: filtered.length,
        items: filtered.slice(offset, offset + limit),
      };
    }
  • compactControl helper: maps a FlatControl to a compact object with id, label, title, section, and applicability.
    function compactControl(c: FlatControl) {
      return {
        id: c.id,
        label: c.label,
        title: c.title,
        section: c.groupPath.join(" › "),
        applicability: c.applicability,
      };
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions pagination and filters but lacks details on pagination defaults, maximum results, sorting, authentication needs, or response format. This is insufficient for a safe agent call.

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?

Two concise sentences front-load the core purpose and filters. No redundant text, though pagination behavior could be more explicit without bloating length.

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 no output schema, no annotations, and 6 parameters, the description is moderately complete. It covers filtering but lacks pagination details, response structure, and version context, leaving gaps for the agent.

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

Parameters2/5

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

Schema description coverage is 50%, and the description repeats information already in the schema for applicability, group, and labelPrefix. It adds no new meaning for version, limit, or offset, leaving those parameters underdocumented.

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

Purpose4/5

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

The description uses specific verbs ('Returns') and resource ('list of ISM controls'), clearly stating it is paginated and filterable. It indirectly differentiates from siblings like get_control (single) and search_controls (broader search) by emphasizing filtering capabilities.

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?

No explicit guidance on when to use this tool versus alternatives like get_control, get_controls, or search_controls. The description implies use for filtered listing but does not state when not to use it or provide context for selection among siblings.

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/RusticEagle/ism-mcp'

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