File size: 3,538 Bytes
32a7beb 85e599a 32a7beb 85e599a 32a7beb 85e599a 32a7beb 85e599a 32a7beb 85e599a 32a7beb 85e599a 32a7beb 85e599a 32a7beb 85e599a 32a7beb 85e599a 32a7beb 85e599a 32a7beb 85e599a 32a7beb | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 | # U3 sqlite-tier task fixture (spec §5). The official reference `sqlite`
# server is not currently present in github.com/modelcontextprotocol/servers
# (checked at commit d31124c, 2026-07-06) — see servers/sqlite_server.py's
# module docstring for the disclosed fallback used instead.
# Fixture: u3_sqlite/fixture.db — two tables, "employees" (3 rows) and
# "inventory" (2 rows), deterministic content.
# {root} is substituted at runtime with the sandboxed copy's absolute path;
# every tool operates on {root}/fixture.db via $QUANTMCP_U3_ROOT, so no task
# instruction actually needs to mention the path (unlike the filesystem/git
# tiers, whose tools take an explicit path argument).
# Instructions are phrased naturalistically and never name the tool to
# call, for the same reason as the U1/U2 tasks.
# `tool:` on each task (Phase 7) declares which tool that task is designed
# to exercise, for the per-tool SCI-vs-Δ regression (H2) -- all 4 sqlite
# tools already had task coverage, so no new tasks were added here; only
# the tool metadata is new.
tasks:
- id: u3-list-tables
instruction: "What tables exist in this database?"
tool: list_tables
checker:
name: call_result_contains
args: {index: 0, contains: "employees"}
- id: u3-describe-employees
instruction: "What columns does the employees table have?"
tool: describe_table
checker:
name: call_result_contains
args: {index: 0, contains: "salary"}
- id: u3-describe-inventory
instruction: "What columns does the inventory table have?"
tool: describe_table
checker:
name: call_result_contains
args: {index: 0, contains: "quantity"}
- id: u3-query-engineering
instruction: "Which employees work in the Engineering department?"
tool: read_query
checker:
name: call_result_contains
args: {index: 0, contains: "Alice Chen"}
- id: u3-query-salary
instruction: "What is Carla Diaz's salary?"
tool: read_query
checker:
name: call_result_contains
args: {index: 0, contains: "72000"}
- id: u3-query-widget-count
instruction: "How many widgets are currently in inventory?"
tool: read_query
checker:
name: call_result_contains
args: {index: 0, contains: "42"}
- id: u3-update-gadget-quantity
instruction: "Update the inventory so the gadget quantity becomes 100."
tool: write_query
checker:
name: sqlite_query_scalar
args:
db_filename: fixture.db
query: "SELECT quantity FROM inventory WHERE item = 'gadget'"
expected: "100"
- id: u3-give-raise
instruction: "Give Bob Martins a raise: set his salary to 90000."
tool: write_query
checker:
name: sqlite_query_scalar
args:
db_filename: fixture.db
query: "SELECT salary FROM employees WHERE name = 'Bob Martins'"
expected: "90000"
- id: u3-delete-widget
instruction: "Remove widget from the inventory entirely."
tool: write_query
checker:
name: sqlite_query_scalar
args:
db_filename: fixture.db
query: "SELECT COUNT(*) FROM inventory WHERE item = 'widget'"
expected: "0"
- id: u3-insert-employee
instruction: >-
Add a new employee named Dana Kim in the Marketing department with a
salary of 65000.
tool: write_query
checker:
name: sqlite_query_scalar
args:
db_filename: fixture.db
query: "SELECT salary FROM employees WHERE name = 'Dana Kim'"
expected: "65000"
|