Skip to main content
Glama

locate_feature_entrypoints

Rank candidate symbols in a reference snapshot by natural-language feature match and call-graph centrality to identify relevant feature entrypoints.

Instructions

Ranks symbols inside a ReferenceSnapshot matching a natural-language feature query and call-graph centrality.

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>",
      "featureQuery": "<featureQuery>"
    },
    "name": "locate_feature_entrypoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNo
snapshotIdYes
featureQueryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses very little: it does not say whether the call is read-only, whether ranking is deterministic, what the ordering or scoring means, or how results are truncated. "Ranks" hints at a read, but nothing confirms mutation safety or side effects.

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 no filler or redundancy; the verb and both ranking criteria arrive immediately. Its brevity is efficient, though it is brevity born of under-specification rather than disciplined editing.

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 three-parameter, no-annotation, no-output-schema tool, the description leaves too much open: return shape, result count, ranking semantics, and the source of snapshotId are all unstated. An agent could call it, but would be guessing about inputs and output.

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%, so all three parameters are undocumented in structured fields. The description glosses featureQuery ("natural-language feature query") and weakly implies snapshotId via "inside a ReferenceSnapshot," but maxResults is never explained — no default, no cap, no effect on ranking vs truncation.

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 ("Ranks") plus the resource ("symbols inside a ReferenceSnapshot") and both ranking criteria (natural-language feature query and call-graph centrality), so the agent knows exactly what comes back conceptually. It stops short of distinguishing itself from siblings such as slice_engine_graph or profile_target_vibe, which also sound like graph-analysis operations.

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 guidance, no mention of prerequisites (e.g. that snapshotId must come from ingest_reference), and no named alternative for a plain symbol lookup. The agent must infer the entry point of the workflow from the name alone.

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