What happens
The server instructions tell the client to call get_prompt_examples alongside get_datasource_schema before writing SQL ("Examples-first — call get_prompt_examples and mirror the closest match"). In practice a claude.ai client often doesn't.
Observed on a local test deployment on 2026-09-12 (client model claude-sonnet-4-6, synthetic ServiceNow-shaped data), across three chats about incidents assigned to the signed-in user:
| Chat |
Called get_prompt_examples? |
What it did instead |
| "are there tickets or incidents assigned to me" |
No |
list_datasources → get_datasource_schema ×2 → wrote SQL from the schema |
| "show me tickets assigned to sandeep" |
No |
Reused the previous turn's schema context and wrote SQL |
| "check the stored examples with get_prompt_examples and then…" |
Yes, only because the user named the tool |
Passed an area that excluded the one relevant stored example (it ranks first with no area, and is absent under the area the client chose) |
The answers happened to be correct each time, but the example library, which is where curated corrections live, was skipped or narrowed away. A deployment that relies on stored examples to steer SQL isn't getting them.
Why it matters
- Curated corrections don't take effect unless the client happens to call the tool.
- An
area the client guesses can silently filter out the best match. Nothing in the result says a better example exists outside that area.
Possible directions (not decided)
- Make the instruction harder to skip, e.g. state it on
get_datasource_schema's own description, which clients do read and call every time.
- Return the top few matching examples inside
get_datasource_schema's result, so they arrive without a second call.
- When
area is passed and a higher-scoring example exists outside it, say so in the result.
Done when
On a scripted run of self-referential and named-person questions, the client sees the most relevant stored example on every question without being told to call a specific tool.
What happens
The server instructions tell the client to call
get_prompt_examplesalongsideget_datasource_schemabefore writing SQL ("Examples-first — call get_prompt_examples and mirror the closest match"). In practice a claude.ai client often doesn't.Observed on a local test deployment on 2026-09-12 (client model
claude-sonnet-4-6, synthetic ServiceNow-shaped data), across three chats about incidents assigned to the signed-in user:get_prompt_examples?list_datasources→get_datasource_schema×2 → wrote SQL from the schemaareathat excluded the one relevant stored example (it ranks first with no area, and is absent under the area the client chose)The answers happened to be correct each time, but the example library, which is where curated corrections live, was skipped or narrowed away. A deployment that relies on stored examples to steer SQL isn't getting them.
Why it matters
areathe client guesses can silently filter out the best match. Nothing in the result says a better example exists outside that area.Possible directions (not decided)
get_datasource_schema's own description, which clients do read and call every time.get_datasource_schema's result, so they arrive without a second call.areais passed and a higher-scoring example exists outside it, say so in the result.Done when
On a scripted run of self-referential and named-person questions, the client sees the most relevant stored example on every question without being told to call a specific tool.