Skip to main content
Glama
krusch-frontend-mcp

krusch-frontend-mcp

by kruschdev

frontend_traverse_graph

Read-onlyIdempotent

Traverse parent/child memory lineage for frontend design rules to trace provenance and related RAG items from a given ID.

Instructions

Company Brain Substrate (SQLite): Graph Traversal. Traverses parent/child memory lineage for frontend design rules.

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": {
      "id": "<id>"
    },
    "name": "frontend_traverse_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ID of the frontend RAG item to traverse from.
depthNoDefault is 3.
directionNoDefault is 'all'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the store is a SQLite-backed substrate and that traversal is over lineage edges, but says nothing about what a traversal returns, how depth limits interact with cycles, or behavior when the node has no parents/children.

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?

Two short sentences, with the operative statement (what is traversed) placed after a brief substrate label. No wasted clauses, though the leading "Company Brain Substrate (SQLite): Graph Traversal" segment is largely redundant with the tool name.

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?

A three-parameter read-only traversal with no output schema and strong annotations needs only modest prose, and the description covers the intent. It falls short on result shape and traversal edge cases, which an agent would want before choosing depth and direction values.

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 description coverage is 100%, with `id`, `depth` (default 3), and `direction` (parents/children/all enum) fully documented inline. The description adds no meaning beyond that — it never explains what depth counts (hops, generations) or how 'all' combines directions, so the baseline 3 applies.

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 ("Traverses") and resource ("parent/child memory lineage for frontend design rules"), which is meaningfully distinct from siblings like frontend_get_provenance or query_design_rules. Minor noise from the "Company Brain Substrate (SQLite): Graph Traversal" prefix, which restates branding rather than adding scope.

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?

There is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer from the phrase "memory lineage" whether this or frontend_get_provenance is the right call, and nothing states the difference between walking lineage vs. querying design rules.

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