site-intelligence-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | Yes | Your RapidAPI key for the Site Intelligence API. Required. | |
| BEELOCATE_RAPIDAPI_HOST | No | RapidAPI host for the Site Intelligence API. | site-intelligence-api.p.rapidapi.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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| site_scoreA | Score a geographic coordinate for ecological and agricultural land suitability. Analyses satellite and climate data for the area around a point and returns a weighted suitability score plus per-metric breakdown: vegetation health, water access, precipitation, terrain, cropland proximity, urbanisation pressure, climate, and distance to infrastructure. Use for site selection and land assessment — agtech, precision agriculture, ecological field research, conservation planning, environmental consulting, apiculture. Not a weather forecast and not a property-value estimate. Each call runs a live satellite computation and takes roughly 25-40 seconds; a smaller radius_m is faster. Prefer one call over several exploratory ones. Args: lat: Latitude, -90 to 90. lon: Longitude, -180 to 180. radius_m: Analysis radius in metres, 200 to 5000. Defaults to 2000. month: Month 1-12 to evaluate seasonally. Omit for an annual view. detail: "summary" returns scores only; "full" adds per-metric raw diagnostics, which is considerably larger. |
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 confusion or overlap with other tools. The tool has a clear, singular purpose of scoring a coordinate for suitability.
The single tool name 'site_score' is descriptive and follows a readable noun_verb convention. However, with only one tool there is no established pattern to evaluate consistency across the set.
A single tool feels too thin for an MCP server focused on site intelligence. While the tool itself is substantive, the server's scope would reasonably include at least a few related operations, such as batch comparison or historical analysis.
The server only offers live scoring of one coordinate at a time. Obvious gaps include no way to compare multiple candidate sites, no batch processing, and no persistence or historical trend analysis, which are common needs in site selection and land assessment.