Skip to main content
Glama
Sign In
Latent Defense MCP Server

Latent Defense MCP Server

Official
by latent-defense
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

oracle_list_nodes

Browse nodes in the loaded infrastructure graph, filtering by type to discover attack paths and triage findings.

Instructions

Browse nodes in the loaded graph, optionally filtered by type.

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": "oracle_list_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_typeNoall
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description must disclose behaviors. It only mentions filter by type, but omits pagination, sorting, or result format. Minimal disclosure of what 'browse' entails.

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?

Single sentence with front-loaded purpose. No wasted words, but trade-off with completeness.

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?

Despite simplicity, missing behavioral details (pagination, ordering) and no annotation support. Incomplete for an agent to fully understand usage.

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?

0% schema coverage; description only mentions 'optionally filtered by type' matching node_type, but no detail on limit parameter or accepted values. Adds little beyond schema names.

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?

Description clearly states verb 'browse' and resource 'nodes in the loaded graph' with optional filtering. Differentiates from sibling tools like oracle_get_node (single node) and oracle_search_nodes (search).

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?

Implies usage for listing nodes with optional filter, but no explicit guidance on when to use this vs alternatives like oracle_search_nodes or oracle_get_node. No when-not or context provided.

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