codesurface
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the indexed API by keyword. Find classes, methods, properties, fields, and events. Returns ranked results with signatures. Args: query: Search terms (e.g. "MergeService", "BlastBoard", "GridCoord") n_results: Max results to return (default 5, max 20) member_type: Optional filter — "type", "method", "property", "field", or "event" file_path: Optional path prefix or exact file to scope results (e.g. "src/services/" or "src/services/foo.ts") include_tests: If true, include test files in results (default false) |
| get_signatureA | Look up the exact signature of an API member by name or FQN. Use when you need exact parameter types, return types, or method signatures without reading the full source file. Args: name: Member name or FQN, e.g. "TryMerge", "CampGame.Services.IMergeService.TryMerge" file_path: Optional path prefix to scope the lookup include_tests: If true, include test files in results (default false) |
| get_classA | Get a complete reference card for a class — all public members. Shows every method, property, field, and event with signatures. Replaces reading the entire source file. Args: class_name: Class name, e.g. "BlastBoardModel", "IMergeService", "CampGridService" file_path: Optional path prefix to scope the lookup include_tests: If true, include test files in results (default false) |
| get_statsA | Get a quick overview of the indexed codebase. Shows file count, record counts by type, and namespace breakdown. |
| reindexA | Incrementally update the index by re-parsing only changed, new, or deleted files. Uses file modification times to detect changes. Fast on large codebases — only touches files that actually changed since the last index. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: get_class for full class reference, get_signature for specific member signatures, get_stats for overview statistics, reindex for incremental indexing, and search for keyword-based discovery. No functional overlap exists.
All tool names follow a consistent verb_noun pattern using snake_case (get_class, get_signature, get_stats, reindex, search). The naming is predictable and intuitive.
Five tools are well-scoped for a code indexing server: providing search, member details, class overview, statistics, and index maintenance. This count is neither too sparse nor too heavy.
The tool set covers all essential operations for code exploration and indexing: searching, retrieving member signatures, getting full class documentation, viewing codebase statistics, and incremental reindexing. No obvious gaps for the stated purpose.