Vegetable Yield Percentage MCP
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_vegetable_yieldA | USDA edible yield percent for a raw vegetable or fruit (the share left after removing peel, seeds, core, stems and trimmings), the refuse percent and what the refuse is, plus USDA household weights (1 medium, 1 cup chopped, 1 clove) and the as-purchased weight of one whole item. From USDA SR28 refuse data. |
| calculate_edible_weightB | Edible weight and trim waste from a purchased (as purchased, untrimmed) weight of a raw vegetable or fruit, using the USDA edible yield percent. |
| calculate_amount_to_buyA | How much of a raw vegetable or fruit to buy for a recipe amount. Give the prepared amount in g, kg, oz or lb, or as a USDA household measure such as "cup chopped", "cup sliced", "medium" or "clove". Returns the edible weight needed, the as-purchased weight to buy at the USDA edible yield, and the number of whole items (for example medium onions) to buy. |
| list_vegetable_yieldsA | List raw vegetables and fruits with their USDA edible yield percent, filtered to fruit or vegetable and sorted by name, lowest yield or highest yield. |
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 4 tools
Each tool has a distinct role: one lookup of yield data, one list/search, and two calculations in opposite directions (trimming a purchased weight vs. scaling up from a recipe amount). The two calculate_ tools do touch the same edible-yield concept, which could cause occasional misselection, but the descriptions make the direction of each clear.
All four tools use a consistent snake_case verb_noun pattern (get_, calculate_, calculate_, list_) with clear object naming. No mixing of conventions or casing styles.
Four tools is well-scoped for a narrow, focused domain (USDA vegetable yield lookup and yield-based calculations). Each tool earns its place with no obvious redundancy.
The surface covers per-item lookup, enumeration/filtering, trim calculation, and purchase-amount calculation, covering the core workflow end to end. Minor gaps exist (e.g. no bulk/multi-item calculations or cooked-yield handling), but agents can work around these with repeated calls.