lamp.
ResourcesPricingAbout

Tool schema

A tool schema is the written description of a tool an agent may use: its name, what it does, the inputs it needs and the form of its result.

What it means

The agent decides which tool to use by reading these descriptions. A vague schema leads to wrong choices; a precise one makes correct use likely. It says, for example, that "get_stock_balance" needs an item code in text and a warehouse code, and returns a quantity in units. The system uses the same schema to reject calls that do not fit, such as a missing warehouse or a negative quantity.

Example

A hardware dealer defines a "create_quote" tool requiring customer code, item code, quantity above zero and an optional discount capped at 10 percent. A call with 15 percent discount is refused before any quote exists.

Records and checks

  • Record each schema, its version and who approved changes to it.
  • Verify with deliberately wrong test calls that invalid ones are refused.
  • The system owner checks that descriptions match what each tool really does.

Common mistakes

  • Writing short, ambiguous tool descriptions that make the agent pick the wrong one.
  • Leaving limits, such as a maximum amount, out of the schema and relying on the model to remember them.
Did not find your answer?Message the lamp team on WhatsApp. Ask about setup, your records, or anything we have not covered here.Ask us on WhatsApp →