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_get_scanning_agent

Retrieve detailed information about a specific scanning agent, including its status and configuration, to monitor and manage DAST scanning agents.

Instructions

Get details of a specific scanning agent.

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": {
      "agentId": "<agentId>"
    },
    "name": "probely_get_scanning_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

C2.7/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden. It only says 'Get details,' implying a read operation, but does not disclose what details are returned, whether the operation is idempotent, or any side effects. However, the existence of an output schema partially covers return structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but lacks any structure or front-loading of critical information. It is adequate but not optimized for quick comprehension.

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?

For a simple tool with one parameter and an output schema, the description is insufficient. It fails to link to sibling tools like 'probely_list_scanning_agents', explain prerequisite steps, or clarify parameter expectations, leaving gaps in context.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning beyond the parameter name 'agentId'. It does not explain the format, source, or constraints of the agentId, leaving the parameter entirely opaque.

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 clearly states 'Get details of a specific scanning agent,' using a specific verb ('Get') and resource ('scanning agent'). It distinguishes from sibling 'probely_list_scanning_agents' by implying retrieval of a single agent vs. listing all.

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 guidance provided on when to use this tool, such as that it requires an agentId from 'probely_list_scanning_agents' or any prerequisites. No alternatives or exclusions mentioned.

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