Skip to main content
Glama

Source Ingredients

source_ingredients
Read-onlyIdempotent

Find local ingredient sourcing context for a recipe by passing an ingredient list and city/region; returns regional store and corridor guidance plus a bounded prompt for the host model.

Instructions

Return bundled regional store and corridor context plus a bounded host-model prompt for sourcing. Returns regional sourcing context and a promptForAgent for the host model to complete. Use when the user needs to find ingredients locally; does not perform live search or pricing itself. Pass ingredients from the recipe ingredient list and location from the user city or region.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ingredients": "<ingredients>",
      "location": "<location>"
    },
    "name": "source_ingredients"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYesUser's city/region
ingredientsYesList of ingredients to source

Output Schema

NameRequiredDescriptionDefault
locationYes
ingredientsYes
regionalDataNo
promptForAgentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description's job is to add context — and it does: the tool returns pre-bundled static context plus a 'promptForAgent' that the host model must complete, and it performs no live search or pricing. The one meaningful gap is that it never says how fresh or regionally constrained the bundled store data is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences restate each other — 'Return bundled regional store and corridor context plus a bounded host-model prompt' followed by 'Returns regional sourcing context and a promptForAgent'. The usage and parameter guidance that follows is valuable, but the opening is duplicated and could be one sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values needn't be re-explained, yet the description usefully flags the 'promptForAgent' component and that the host model must complete it. Both required parameters are addressed and the no-live-search limitation is stated, leaving only minor gaps around data freshness and how the returned prompt should be consumed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description earns an extra point by telling the agent where to derive each value: ingredients from the recipe ingredient list, location from the user's city or region. That provenance guidance is real meaning beyond the schema's 'List of ingredients to source' / 'User's city/region'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and names a concrete resource: 'Return bundled regional store and corridor context plus a bounded host-model prompt for sourcing'. It also explicitly delimits scope with 'does not perform live search or pricing itself', which separates it from web-search style siblings. 'Corridor context' and 'bundled' are somewhat jargon-y, keeping it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear trigger ('Use when the user needs to find ingredients locally') and an explicit exclusion ('does not perform live search or pricing itself'), which steers the agent away from expecting real-time results. It stops short of naming a concrete alternative sibling for that search/pricing need, so the routing is implied rather than complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.