Skip to main content
Glama
gawakawa

Pursuit MCP

by gawakawa
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

Pursuit MCP

MCP server providing Pursuit integration for PureScript documentation search.

Features

  • Search Pursuit for PureScript functions, types, modules, and packages

  • Type signature search support

  • Access to comprehensive PureScript package documentation

Related MCP server: OpenTelemetry Documentation MCP Server

Usage

MCP Client Configuration

Add to your MCP client configuration (e.g., Claude Desktop):

{
  "mcpServers": {
    "pursuit": {
      "command": "nix",
      "args": ["run", "github:gawakawa/pursuit-mcp", "--"]
    }
  }
}

Available Tools

search_pursuit

Search Pursuit for PureScript functions, types, and documentation.

Parameters:

  • query (string): Search query (function name, type signature, or keyword)

  • limit (integer, optional): Maximum number of results to return (default: 10)

Examples:

  • Function name search: map

  • Type signature search: (a -> b) -> f a -> f b

  • Module search: Data.Array

  • Package search: prelude

Response Format: Each result includes:

  • package: Package name (e.g., "purescript-prelude")

  • version: Package version

  • info: Result type and metadata

    • For declarations: includes module, title, type signature

    • For packages: includes deprecation status

    • For modules: includes module name

  • text: Plain text documentation

  • url: Direct link to the documentation

  • markup: HTML-formatted documentation (optional)

License

MIT

Available Tools

1 tool
search_pursuitB

Search Pursuit for PureScript functions, types, and documentation.

Args: query: Search query (function name, type signature, or keyword) limit: Maximum number of results to return (default: 10)

Returns: Formatted search results from Pursuit as JSON string

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the return format (JSON string) and default limit, but lacks details on error handling, rate limits, authentication needs, or search behavior (e.g., partial matches, case sensitivity). For a search tool with zero annotation coverage, this is insufficient.

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

Conciseness4/5

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

The description is well-structured with clear sections (Args, Returns) and front-loaded purpose. It's concise with no wasted words, though the 'Returns' section could be integrated more smoothly. Every sentence adds value.

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 tool's moderate complexity (2 parameters, search functionality), the description covers purpose, parameters, and return format. With an output schema present, it doesn't need to detail return values. However, it lacks behavioral context like error cases or search specifics, leaving some gaps.

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 0%, so the description must compensate. It explains both parameters: 'query' as search query for function names, type signatures, or keywords, and 'limit' as maximum results with a default. This adds meaningful context beyond the bare schema, though it could detail query syntax or limit constraints more.

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 clearly states the tool searches for PureScript functions, types, and documentation, specifying the resource (Pursuit) and verb (search). It distinguishes what can be searched (functions, types, documentation) but doesn't need sibling differentiation since there are no sibling tools. The purpose is specific and unambiguous.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It only states what the tool does, not the context for its application. With no sibling tools, this is less critical, but still lacks usage context.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedsearch_pursuit
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clear purpose: searching the Pursuit database for PureScript-related content. An agent cannot misselect between non-existent alternatives.

Naming Consistency5/5

The single tool name 'search_pursuit' follows a consistent verb_noun pattern, using snake_case. There are no other tools to compare against, so no inconsistency can exist. The naming is clear and predictable for its isolated context.

Tool Count2/5

A single tool is too few for a server named 'Pursuit MCP', which suggests broader functionality related to PureScript's Pursuit ecosystem. While the tool covers search, obvious gaps exist (e.g., no tools for browsing packages, viewing documentation details, or managing favorites), making the server feel thin and incomplete for its implied domain.

Completeness2/5

The tool set is severely incomplete for a Pursuit-related server. It only provides search functionality, missing essential operations like retrieving detailed package information, listing categories or modules, or accessing documentation beyond search results. This creates significant gaps that will limit agent capabilities in handling PureScript queries effectively.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers