Farm OS MCP Server
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 |
|---|---|
| get_farm_infoB | Get information about a specific farm. Args: farm_id: The unique identifier for the farm (e.g., 'farm_001') Returns: Dictionary containing farm information |
| list_all_farmsB | List all available farms. Returns: List of all farms with basic information |
| get_field_infoB | Get information about a specific field. Args: field_id: The unique identifier for the field (e.g., 'field_001') Returns: Dictionary containing field information |
| list_fields_by_farmB | List all fields for a specific farm. Args: farm_id: The unique identifier for the farm Returns: List of fields belonging to the farm |
| get_livestock_infoC | Get information about specific livestock. Args: livestock_id: The unique identifier for the livestock group Returns: Dictionary containing livestock information |
| list_livestock_by_farmB | List all livestock for a specific farm. Args: farm_id: The unique identifier for the farm Returns: List of livestock belonging to the farm |
| get_equipment_infoC | Get information about specific equipment. Args: equipment_id: The unique identifier for the equipment Returns: Dictionary containing equipment information |
| list_equipment_by_farmB | List all equipment for a specific farm. Args: farm_id: The unique identifier for the farm Returns: List of equipment belonging to the farm |
| get_sensor_readingsC | Get all sensor readings for a specific field. Args: field_id: The unique identifier for the field Returns: List of sensor readings for the field |
| search_by_crop_typeA | Search for fields by crop type. Args: crop_type: The type of crop to search for (e.g., 'Corn', 'Wheat') Returns: List of fields matching the crop type |
| get_farm_summaryC | Get a comprehensive summary of a farm including all its assets. Args: farm_id: The unique identifier for the farm Returns: Dictionary containing comprehensive farm summary |
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 11 tools
Every tool has a clearly distinct purpose targeting specific resources (equipment, farms, fields, livestock, sensors) with no overlap in functionality. The get_* tools retrieve specific entities, list_* tools enumerate resources by farm, and search_by_crop_type provides unique filtering capability.
All tools follow a consistent verb_noun pattern with snake_case throughout. The naming convention is perfectly predictable: get_* for retrieving specific entities, list_* for enumerating collections, and search_* for filtering operations.
With 11 tools, this is well-scoped for a farm management system. Each tool earns its place by covering distinct aspects of farm operations including equipment, farms, fields, livestock, and sensors without being overwhelming.
The server provides excellent read operations but lacks any write/update capabilities. For a farm management system, obvious gaps include creating/updating farms, fields, equipment, or livestock records, and managing sensor data. The surface is complete for querying but incomplete for full lifecycle management.