llm-assure-mcp

list_probes

Lists probes in a specified attack suite, returning each probe’s ID, name, severity, prompts, and detector types so you can inspect available tests before running an assurance assessment.

Instructions

List the probes in one suite (id, name, severity, prompts, detector types).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "suite_id": "<suite_id>"
    },
    "name": "list_probes"
  }
}

Input Schema

Name	Required	Description	Default
`suite_id`	Yes
`pack_dirs`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It implies a read-only listing but does not state whether the call is safe or side-effect free, how many probes may be returned, whether pagination applies, or what pack_dirs does behaviorally. Beyond naming the returned fields, it discloses almost no runtime behavior.

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 a single efficient sentence, with purpose front-loaded and the returned fields parenthesized compactly. It contains no filler, although its brevity contributes to the gaps in parameter and behavioral coverage.

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?

An output schema exists, so the description need not explain the return shape in detail, even though it lists the fields. However, for a two-parameter tool with 0% schema description coverage and no annotations, the missing explanation of pack_dirs and of read-only behavior leaves material gaps.

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 0%, so the description must compensate for both parameters. suite_id is only implied by 'in one suite,' and pack_dirs is not mentioned at all, leaving its meaning and accepted values entirely undocumented. This leaves a required parameter and an optional one with no added meaning.

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?

States a specific verb and resource with scope: 'List the probes in one suite.' This clearly distinguishes it from list_suites, which enumerates suites rather than probes. It also names the fields returned (id, name, severity, prompts, detector types), which reinforces what the tool produces.

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

Usage Guidelines3/5

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

The phrase 'in one suite' implies that the tool is used when the caller already knows a suite id, and the required suite_id parameter reinforces that scope. The description does not explicitly state when to use this tool instead of get_findings or run_assessment, and it gives no exclusions or prerequisites.

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

Deploy Server