Skip to main content
Glama
Wildcard-Official

DeepContext

Official
by Wildcard-Official
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JINA_API_KEYNoAPI key for Jina AI embeddings and reranker (required for self-hosting)
WILDCARD_API_KEYNoAPI key for using the Wildcard backend (required for quickstart)
TURBOPUFFER_API_KEYNoAPI key for Turbopuffer vector storage (required for self-hosting)

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

CapabilityDetails
tools
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
index_codebaseA
<parameter name="force_reindex" required="false">
  <type>boolean</type>
  <description>Force complete reindexing even if already indexed</description>
  <default>false</default>
  <when_to_use>Code has changed significantly or search results seem outdated</when_to_use>
</parameter>
search_codebaseA
<parameter name="codebase_path" required="true">
  <type>string</type>
  <description>ABSOLUTE path to the codebase directory to search</description>
  <examples>
    <valid>/Users/name/project</valid>
    <valid>/home/user/code/repo</valid>
    <invalid>.</invalid>
    <invalid>../project</invalid>
    <invalid>relative/path</invalid>
  </examples>
  <validation>Must be absolute path starting with / (Unix) or C:\ (Windows)</validation>
</parameter>

<parameter name="max_results" required="false">
  <type>number</type>
  <description>Maximum number of code chunks to return</description>
  <default>5</default>
  <best_practice>Keep at default 5 for focused results. Use multiple targeted searches rather than increasing this limit</best_practice>
</parameter>

Code chunks with file paths, line numbers, relevance scores, symbol information, imports, and exports Codebase must be indexed first with index_codebase

get_indexing_statusA

Enhanced indexing status with completion statistics when available

clear_indexA

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Codebase StatusCurrent status of indexed codebases
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: indexing, searching, checking status, and clearing. No overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (index_codebase, search_codebase, get_indexing_status, clear_index), making them predictable and readable.

Tool Count5/5

Four tools is well-scoped for a codebase indexing/search domain. Each tool earns its place and there is no unnecessary bloat.

Completeness5/5

The set covers the full lifecycle: index, search, check status, and clear. Force_reindex and optional path parameters provide flexibility, so no obvious gaps exist.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources