mcp-server-blm-mlrs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP mode; if set, server runs over HTTP on that port instead of stdio. | |
| DATABRICKS_APP_PORT | No | Alternative port for HTTP mode (same effect as PORT). |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_lease_detailsA | Retrieve details for a BLM geothermal lease by its Case Serial Number. |
| search_leasesA | Search BLM geothermal leases, optionally filtering by state, status, and effective-/expiration-date ranges. All parameters are optional. If none is provided, all leases are returned (capped at 50 records). |
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 2 tools
get_lease_details and search_leases have clearly distinct purposes: one retrieves a specific lease by serial number, while the other returns a list of leases matching filters. There is no overlap or ambiguity between them.
Both tools use verb-led names (get, search), but the object phrasing differs slightly ('lease_details' vs 'leases'). This is a minor deviation from a strict verb_noun pattern, but the naming is still predictable and readable.
The server has only 2 tools, which feels thin for a general-purpose server. However, the domain is narrowly focused on querying BLM geothermal leases, making this a borderline but reasonable count for a read-only lookup service.
The two tools cover the core workflow of searching for leases and retrieving full details for a specific lease. There are no obvious gaps for the stated purpose of querying lease information, though additional filters or related data could enhance completeness.