Skip to main content
Glama

Draft a botanical sourcing brief

build_sourcing_brief
Read-onlyIdempotent

Generate an RFQ draft for a catalog ingredient. Returns text only: does not store personal data, submit an inquiry, contact a supplier or place an order. Review the draft before using the website inquiry form.

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": {
      "ingredientSlug": "<ingredientSlug>"
    },
    "name": "build_sourcing_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
gradeNo
notesNo
quantityNo
applicationNo
destinationNo
ingredientSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: it returns text only, stores no personal data, and does not submit an inquiry, contact a supplier, or place an order. That explicitly rules out side effects an agent might otherwise assume from an 'RFQ' tool.

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

Conciseness5/5

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

Two tight sentences with zero waste. The core action is front-loaded, and the negative constraints follow immediately, so an agent can parse intent and limits at a glance.

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

Completeness3/5

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

The description adequately covers the return value ('text only') and the side-effect boundary, which matters given there is no output schema. But for a six-parameter tool with no schema descriptions, the absence of any parameter guidance leaves a real gap in completeness.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, so the description carries the full burden of explaining them. It only hints at ingredientSlug via 'catalog ingredient' and says nothing about grade, quantity, application, destination, or notes, leaving most inputs unexplained in both schema and prose.

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 states a specific verb and resource: 'Generate an RFQ draft for a catalog ingredient.' That is clearly distinct from the calculate_*, get_*, and search_* siblings, which compute costs or retrieve records. It stops short of naming an alternative, but the purpose is unambiguous.

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

Usage Guidelines3/5

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

The closing sentence 'Review the draft before using the website inquiry form' implies the workflow context: this tool produces a draft that feeds a later manual step. However, it gives no explicit when-to-use versus when-not guidance and does not point to any sibling tool for related tasks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.