Clearspar Part 135 MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLEARSPAR_API_KEY | Yes | API key for authentication (required) | |
| CLEARSPAR_BASE_URL | No | Base URL for the Clearspar API | https://clearspar.binnacleai.com |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| market_summaryA | Analyst summary of a state's Part 135 charter market: operator count, total tails, avg/median fleet, largest operator, top-5 tail share, HHI concentration, and the top operators. Computed live over all operators in the state. |
| fleet_rankingA | Operators ranked by fleet size (FAA tail count). Optionally scope to one state; otherwise ranks the whole ~1,890-operator US universe. |
| compare_operatorsA | Side-by-side comparison of 2+ named operators (state, fleet size, certNo, CRM status), with which is largest and whether they share a state. Names are matched client-side (no server text search). |
| competitive_landscapeA | Competitive structure of a state's Part 135 market: operator count, fleet-size distribution buckets, top-1/3/5 tail concentration, HHI with plain-English interpretation, and the leaders. |
| crm_pipeline_summaryA | Live distribution of operators across CRM stages (NEW/CONTACTED/REPLIED/DEMO/CLOSED/DEAD), optionally scoped to a state. Reflects outreach progress in the dataset. |
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 targets a distinct analytical task: operator comparison, state market structure, CRM pipeline, fleet ranking, and market summary. There is no functional overlap or ambiguity between tools.
All tool names use lowercase with underscores and follow a descriptive pattern (verb_noun or noun_noun), but 'competitive_landscape' uses an adjective rather than a verb, creating a slight inconsistency.
With 5 tools, the server is well-scoped for its purpose of analyzing Part 135 charter operators. Each tool fills a distinct and necessary role without excess or deficiency.
The tool set covers core analytical needs (comparison, market structure, CRM, ranking, summary) but lacks a tool for viewing detailed information about a single operator, which would be a minor but useful addition.