// notes from an old coder -- php, databases, and the occasional rant
For codebase Q&A, retrieve the relevant files first, then generate. A 200k context window is not a search index.
After connecting, list tools and confirm names, descriptions, and schemas. A renamed tool silently breaks old prompts that hardcode the name.
An MCP server can expose tools that read files or hit the network. Pin versions, review the tool list, and run untrusted servers in a sandbox.
A tool that both writes a row and sends email is hard to retry and hard to audit. Split side effects so the agent can recover mid-flight.
Tool JSON schemas should be as strict as an HTTP contract: required fields, enums, and no extra properties. Loose schemas produce unusable arguments.
When the model must pick a tool and fill JSON arguments, a low temperature reduces schema drift and invented function names.
Put non-negotiable rules in the system (or developer) message so they survive noisy user turns. The model treats that channel as the contract for the whole session.
// showing 1-7 of 7 posts • page 1/1