A supplier directory that does not rot: contacts, terms, lead times, review dates.
Strong domain-specific tool design with clear naming (verb_noun pattern), comprehensive parameter schemas, and detailed descriptions. All 9 tools have explicit input schemas with type definitions and field descriptions. Descriptions average ~180 chars, within the 10-1024 baseline. However, output schemas are not formally documented in the code, and error handling lacks recovery guidance. Tool composition is excellent, each tool has a single responsibility, and parameter naming is consistent (supplier identifier accepts both ID and name). Free/Pro tier gating is implemented but not reflected in tool annotations.
Add a supplier to the directory and return its SUP-YYYY-NNNN number: the name, what they supply, who to contact and how, the payment terms, the lead time in days, and notes. Free tier: 10 suppliers; removing one you no longer use frees its slot.
List suppliers whose records are due for review: last_reviewed is null or older than the review interval (default 90 days). Pro tier only.
Export the supplier directory as CSV: id, name, category, contact, email, phone, website, address, payment terms, lead time, notes, last reviewed. Reads only.
Export the supplier directory as Markdown table: id, name, category, contact, email, phone, website, address, payment terms, lead time, notes, last reviewed. Pro tier only.
Read one supplier record in full by SUP number or name: every contact field, the payment terms, the lead time, the notes, and when the record was last reviewed. Reads only.
List the supplier directory A to Z by name: contact, payment terms, lead time, when each record was last reviewed and how many days ago that was. Filter by category and by free text across every field. Reads only.
Output schemas not formally documented. Tool descriptions state what is returned (e.g., 'SUP-YYYY-NNNN number', 'CSV export') but JSON Schema output definitions are absent from the code. LLMs cannot reliably parse response structure or plan downstream tool calls.
Error handling lacks recovery guidance. Code includes validation (checkDate, checkEmail) and throws errors, but error responses do not guide the LLM on next steps. E.g., 'cannot read a date' should suggest 'Use YYYY-MM-DD format' or 'Call supplier_get() to see current format'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
Stamp a supplier record with today's date to mark it reviewed: you have checked the record against reality and it is still true. Clears the due-review flag.
Remove a supplier from the directory by SUP number or name. Frees its slot on the free tier.
Change any of a supplier's fields by SUP number or name: name, category, the contact fields, payment terms, lead time, notes.
Tool annotations missing. supplier_remove is destructive and supplier_list is read-only, but no destructiveHint or readOnlyHint annotations are present in the tool registration. This prevents clients from applying safety policies (e.g., requiring confirmation before delete).
Free/Pro tier gating not exposed to LLM. supplier_due_review and supplier_export_markdown are Pro-only, but the tool descriptions do not state this. An LLM on a free tier will attempt these tools and receive cryptic errors instead of being guided to upgrade or use free alternatives.
Pagination not implemented for list tools. supplier_list and supplier_export_* do not accept limit/offset or return a total count. If a user has hundreds of suppliers, the entire list is returned, risking context window exhaustion.