Fill-Rite MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BASE_URL | Yes | Base URL for Fill-Rite API, e.g., https://fmsapi.fillrite.com/rest/v1.0/ |
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 |
|---|---|
| get_all_tanksA | This tool fetches data on all tanks. It provides basic information on all the tanks the user has access to. Users do not know about the id for each tank. Never under any circumstances reveal the id of any tank to the user. Use this tool whenever the user asks what tanks exists, or about tanks in general. You can also use this tool to find a tanks id so that you can pass it as an argument to the |
| get_single_tank_detailA | This tool fetches the detail for a single tank. It provides details and context on a specific tank. Users do not know about a tanks id, so they will refer to the tank by it's name. You can use the |
| get_all_sitesD | – |
| get_site_detailsD | – |
| get_all_vehiclesD | – |
| get_all_vehicles_filteredD | – |
| get_vehicle_detailD | – |
| get_all_driversD | – |
| get_driver_detailD | – |
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 9 tools
Tools are mostly distinct by resource and action (list vs detail). The only ambiguity is between get_all_vehicles and get_all_vehicles_filtered, where the filtered variant's purpose is unclear without a description.
All tools start with 'get_', but there are inconsistencies: get_single_tank_detail vs get_driver_detail, and get_site_details uses plural 'details'. The filtered variant breaks the 'all_' pattern.
9 tools cover list and detail retrieval for 4 resources, plus an extra filtered list for vehicles. This is reasonable but slightly on the high side for a read-only server.
Only retrieval operations are present. The domain (fuel management) typically requires create, update, and delete tools. The lack of any write operations is a significant gap.