Skip to main content
Glama
timohaa

Scopewalker MCP

by timohaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_functions

Retrieve function and method information from a codebase, including line counts, and filter by keywords, extensions, or depth to analyze code structure.

Instructions

Returns function/method info. Use detail=lines for line counts per function.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
grepNoFilter by keyword
pathYesTarget path
limitNoMax results
detailNoDetail level
sort_byNoSort order
max_depthNoMax depth
max_filesNoMax files to scan
min_linesNoMin lines (lines mode)
extensionsNoFilter by extensions
include_hiddenNoInclude hidden
ignore_patternsNoExclude patterns

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.3.0
    • addedInput schema / properties / extensions / items / maxLength
      Added value: +32
    • addedInput schema / properties / extensions / items / pattern
      Added value: +"^\\.?[A-Za-z0-9_+-]+$"
    • addedInput schema / properties / extensions / maxItems
      Added value: +100
    • addedInput schema / properties / ignore_patterns / items / maxLength
      Added value: +512
    • addedInput schema / properties / ignore_patterns / maxItems
      Added value: +100
    • changedInput schema / properties / limit / maximum
      Previous value: -9007199254740991New value: +5000
    • changedInput schema / properties / max_depth / maximum
      Previous value: -9007199254740991New value: +64
    • changedInput schema / properties / max_files / maximum
      Previous value: -9007199254740991New value: +10000
    • changedInput schema / properties / min_lines / maximum
      Previous value: -9007199254740991New value: +10000
  2. First observedv1.0.4

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral burden. It conveys that this is a read-style operation ('Returns') and reveals one mode of behavior (detail=lines). However, it does not disclose scanning behavior, defaults, or what counts vs. lines actually means beyond the brief hint.

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?

Two short sentences, no filler. The main purpose is front-loaded and the parameter tip is direct. Every word earns its place.

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 an 11-parameter tool with no output schema and no annotations, the description is minimally adequate. The schema documents all parameters, and the description adds one useful detail-mode hint. However, it does not clarify the default behavior, what 'info' includes, or how it relates to sibling tools like get_line_counts.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds value by explaining that detail=lines yields 'line counts per function,' which is more meaningful than the schema's bare 'Detail level.' That semantic clarification justifies above-baseline scoring.

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 states a clear verb and resource: it 'Returns function/method info,' which is genuinely informative. It does not explicitly differentiate from siblings like get_line_counts or get_code_inventory, so it misses the top score, but the core purpose is unambiguous.

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?

'Use detail=lines for line counts per function' gives a concrete usage instruction for a parameter, implying a use case. However, it does not say when to choose this tool over the closely related sibling get_line_counts, nor does it mention 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