Skip to main content
Glama
dalebrubaker

sourcegraph-mcp

by dalebrubaker
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

search_sourcegraph

Search code across your SourceGraph instance using text, patterns, or regular expressions. Filter by repository, file, language, and more for precise results.

Instructions

General code search across your SourceGraph instance. Use this for text-based searches, finding patterns, or when you need to search for more than just symbol definitions.

Supports full SourceGraph query syntax including:

  • repo:owner/name - Filter by repository

  • file:pattern - Filter by file path

  • lang:language - Filter by programming language

  • case:yes - Case-sensitive search

  • Regular expressions and literals

Examples:

  • 'PlaceOrder lang:csharp' - Find PlaceOrder in C# files

  • 'repo:myorg/myrepo TODO' - Find TODOs in a specific repo

  • 'file:.py$ import pandas' - Find pandas imports in Python files

  • 'error handling lang:java' - Search for error handling in Java

Note: For finding symbol definitions or references specifically, use find_symbol_definition or find_symbol_references for faster, more accurate results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query using SourceGraph syntax
max_resultsNoMaximum number of results (default: 10)

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Discloses supported source syntax and query features with examples, but lacks details on output format or error behavior. Since no annotations exist, description carries burden and does well overall.

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?

Well-structured with bullet points and examples, no wasted words, front-loaded with clear purpose.

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 no output schema and only two parameters, the description is thorough. Missing explicit mention of output format, but examples imply it.

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 covers both parameters (100% coverage), and description adds examples and syntax details beyond the schema's param descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it's for 'general code search' across SourceGraph, and distinguishes from sibling tools for symbol definitions and references.

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

Usage Guidelines5/5

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

Explicitly advises when to use this tool versus find_symbol_definition or find_symbol_references, and provides query syntax examples.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dalebrubaker/sourcegraph-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server