Pursuit MCP
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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 |
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 1 tool
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.
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.
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.
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.