Skip to main content
Glama

slice_engine_graph

Computes the minimal transitive AST call/type closure from entrypoint symbols to strip unrelated boilerplate and map external dependencies to zero-dependency shims.

Instructions

Computes the minimal transitive AST call/type closure starting from entrypoint symbols, stripping 80-98% of unrelated repo boilerplate and mapping external dependencies to zero-dep inline shims.

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": {
      "snapshotId": "<snapshotId>",
      "entrypointIds": "<entrypointIds>"
    },
    "name": "slice_engine_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxDepthNo
snapshotIdYes
includeTypesNo
entrypointIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden, and it does disclose the transformation semantics: transitive closure, aggressive pruning of unrelated code, and external deps replaced by inline shims. It says nothing about whether analysis is read-only or whether artifacts are written, whether the snapshot must be pre-ingested, cost/latency, or determinism. Partial disclosure only, so a middling score.

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?

A single front-loaded sentence with the core operation first and the payoff second; no filler. The density of jargon (transitive closure, zero-dep inline shims) costs some immediate legibility, but every clause adds information.

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 four-parameter analysis tool with no annotations and no output schema, the description leaves too much unspecified: no snapshotId meaning, no return-value shape or how the closure/shims are presented, no guidance on cost or failure modes. The one sentence of intent is a start but not sufficient for confident invocation.

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 description coverage is 0% across four parameters, so the description must compensate and largely fails. It implies entrypointIds (entrypoint symbols), includeTypes (call/type closure), and vaguely maxDepth (minimal transitive), but snapshotId is never mentioned and no defaults, ranges, or depth/limit semantics are given.

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?

Names a specific verb and resource: computes the minimal transitive AST call/type closure from entrypoint symbols, with the concrete effect of stripping 80-98% of boilerplate and inlining zero-dep shims. An agent can distinguish this from siblings like locate_feature_entrypoints or verify_engine_parity. It stops short of an explicit sibling contrast, so 4 rather than 5.

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 when-to-use or when-not-to-use statement, and no alternative is named. The agent must infer that this follows entrypoint discovery (e.g., locate_feature_entrypoints) and precedes parity verification. No prerequisites or preconditions on snapshotId are given.

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