Skip to main content
Glama

jdx_samples

Rank call sites and return source snippets to show how a symbol is used. Filter by workspace, artifact glob, result limit, and snippet length.

Instructions

How is this symbol really used? Ranked call sites with source snippets as evidence.

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": {
      "query": "<query>"
    },
    "name": "jdx_samples"
  }
}

Input Schema

NameRequiredDescriptionDefault
inNoOnly matches from artifacts whose label matches this glob.
limitNoMaximum rows shown (default 3); the rest become a truncation footer.
queryYesThe symbol reference, type, pattern or glob the command asks about. Quote refs containing # or (). Empty only where the command allows it (ls, tree).
excludeNoSkip matches from artifacts whose label matches this glob.
maxLinesNoCap each snippet's shown code lines (default 15).
workspaceNoNamed workspace to answer from (default: the workspace the server was started with). Stored workspaces only.
preferSourcesNoRank callers from sources-paired artifacts first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the two most important traits — results are ranked, and each row carries a source snippet as evidence. It says nothing about result volume, truncation behavior, or depth of traversal, which matter for an evidence-gathering tool.

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, front-loaded with the intent question followed by the concrete deliverable. The rhetorical question is slightly padded relative to a plain statement, but nothing is wasted.

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?

For a seven-parameter, non-annotated tool in a 26-tool family, the definition covers what the tool returns but not how it differs from adjacent usage/caller tools. An agent can call it correctly on parameters but not confidently select it over siblings.

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%, so all seven parameters (including query, in/exclude globs, maxLines, preferSources) are already documented in the schema. The description adds no meaning beyond it, 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 concrete resource and output shape: "Ranked call sites with source snippets as evidence" tells the agent exactly what comes back. However, it never distinguishes itself from near-identical siblings such as jdx_callers, jdx_calls, or jdx_usages, so an agent must guess which one to call.

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?

The opening question implies the use case (seeing real usage of a symbol) but there is no explicit when-to-use, when-not-to-use, or named alternative among the 26 sibling tools. With jdx_usages and jdx_callers present, the absence of any routing guidance is a real gap.

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