Skip to main content
Glama
Sign In
Snyk API & Web MCP Server

Snyk API & Web MCP Server

Official
by snyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

probely_list_scanning_agents

Retrieve scanning agents with optional filters for status, search, and pagination to monitor agent connectivity.

Instructions

List scanning agents. Use status to filter: 'connected', 'connected_with_issues', 'disconnected'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "probely_list_scanning_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
lengthNo
statusNo
searchNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description does not disclose behavioral traits such as pagination behavior, rate limits, authentication needs, or what actions are performed. It only hints at filtering without deeper context.

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 extremely concise with two short sentences. Every word is useful, and it front-loads the main action. No unnecessary content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters (0 required) and an output schema, the description only covers status filtering. It does not mention pagination (page/length), search, or provide any context about the response format. For a list tool, this is incomplete.

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 coverage is 0%, so the description must compensate. It adds value only for the status parameter by listing valid filter values ('connected', 'connected_with_issues', 'disconnected'). However, it completely ignores page, length, and search parameters, leaving them unexplained.

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 clearly states the action ('List scanning agents') and mentions filtering by status. The name and description together make the purpose obvious, but it does not explicitly differentiate from sibling tools like probely_list_scans or probely_list_targets.

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?

The description only says 'Use status to filter', providing minimal guidance on when to use this tool. No mention of when not to use it or alternatives among siblings.

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

Deploy Server

Other Tools