Equation 13 · How Tool Protocols and the Model Context Protocol Actually Work
What does this equation mean?
Read the formula alongside the article passage below. Each part has a deeper page with its role in the equation, the supporting passage and nearby citations.
the model, which is expected — but not forced by anything outside its own training — to emit a call whose name and arguments validate against some tool in . Read the equation part by part below; each part has a contextual explanation and a link to its mathematical background.
Read it piece by piece
Symbol pi_θ
the model, which is expected — but not forced by anything outside its own training — to emit a call whose name and arguments validate against some tool in .
How to interpret it
Read this expression with the definitions, units, and assumptions supplied by the article.
What the article says around this equation
Here is the tool set most recently returned by tools/list , each member carrying its own schema; is the model, which is expected — but not forced by anything outside its own training — to emit a call whose name and arguments validate against some tool in ; is dispatch through the client to the server and back, exactly as described above; and is the context the model reasons over on the next step, built by appending the call and its result to what came before. The assumption is in that last term: is concatenated into the model’s context and fed straight back into with no protocol-level check on what it contains.…
Read the full surrounding passage
Here is the tool set most recently returned by tools/list , each member carrying its own schema; is the model, which is expected — but not forced by anything outside its own training — to emit a call whose name and arguments validate against some tool in ; is dispatch through the client to the server and back, exactly as described above; and is the context the model reasons over on the next step, built by appending the call and its result to what came before. The assumption is in that last term: is concatenated into the model’s context and fed straight back into with no protocol-level check on what it contains. Whatever a tool returns becomes part of what the model reads next, on exactly the same footing as the user’s own words. Once that is stated plainly, the entire security section below is really just an inventory of what happens when , or the tool descriptions inside , are not what they claim to be.
Sources cited in the article section
These citations give research context. Read each source to check which claims it supports.
Return to How Tool Protocols and the Model Context Protocol Actually Work