Skip to main content
Glama
Sign In
Context-MCP

Context-MCP

by yesheng-oss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

codegraph_filter

Filter code graph nodes by type, exports, calls, return type, or file path to find relevant functions, classes, modules, or files. Results sorted by connectedness, with adjustable limit and token budget.

Instructions

Filter graph nodes by semantic properties. Results sorted by PageRank (most connected first). All filters optional — combine freely. node_type: function|class|module|file. exported/side_effect: bool. return_type: substring match. called_by/calls: node name. file_pattern: glob. token_budget: max tokens in response.

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": {
      "path": "<path>"
    },
    "name": "codegraph_filter"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
callsNoOnly nodes that call this name
limitNoMax results (default 20)
exportedNo
called_byNoOnly nodes called by this name
node_typeNo
return_typeNoSubstring match on return type
side_effectNo
file_patternNoGlob pattern for file path
token_budgetNoMax tokens in response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does this well by stating that results are sorted by PageRank, that filters are optional and freely combinable, and by explaining filter value formats. It does not explicitly state whether the operation is read-only or how result nodes are shaped, but 'filter' strongly implies a read-only operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, front-loaded with the core purpose, and then uses a terse parameter key to pack filter semantics into one readable paragraph. Every clause earns its place; nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 10-parameter surface and absence of annotations and output schema, the description provides a strong foundation: it explains filtering semantics, ordering, and token budget. It lacks explicit guidance on what each returned node contains and does not clarify the required 'path' parameter, so it is not fully complete.

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

Parameters4/5

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

The description adds meaningful semantics for many parameters: node_type values, called_by/calls as node names, return_type as substring match, file_pattern as glob, and token_budget as max response tokens. It leaves the required 'path' parameter unexplained and relies on the schema for 'limit', which is a minor gap given 60% schema coverage.

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 opens with a clear verb and resource: 'Filter graph nodes by semantic properties.' It also conveys specific behavior like PageRank ordering and optional filters. It does not explicitly differentiate itself from siblings such as codegraph_query or codegraph_nodes, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage — filter graph nodes by semantic properties — and clarifies that all filters are optional and combinable. However, it gives no explicit guidance on when to choose this tool over its siblings, nor any exclusions or alternatives.

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