Skip to main content
Glama
Sign In
sec-graph

sec-graph

by Vadale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

shortest_path

Find the shortest path connecting two concepts in the knowledge graph to trace data flow between source and sink.

Instructions

Find the shortest path between two concepts in the knowledge graph.

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": {
      "source": "<source>",
      "target": "<target>"
    },
    "name": "shortest_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesSource concept label or keyword
targetYesTarget concept label or keyword
max_hopsNoMaximum hops to consider
project_pathNoAbsolute path to a project directory containing graphify-out/graph.json. Optional — defaults to the graph this server was started with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description must carry the full burden. It only states the high-level function without disclosing algorithm complexity, output format, error handling (e.g., no path found), or other behavioral traits.

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, no extraneous words. However, it lacks structure such as bullet points or separated sections; the minimalism is acceptable but not exemplary.

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 no annotations or output schema, the description should explain what 'concepts' are, what the output looks like, and limitations. It fails to provide enough context for an agent to fully understand the tool's behavior.

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

Parameters3/5

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

Schema covers all 4 parameters with descriptions, so description adds no extra meaning beyond the schema. Baseline 3 is appropriate.

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 states the action (find) and resource (shortest path) clearly, specifying it operates on two concepts in the knowledge graph. It distinguishes from sibling tools like get_node or get_neighbors but does not explicitly differentiate itself.

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 on when to use this tool versus alternatives like query_graph or get_neighbors. No prerequisites 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