← Mathematical compendium

Published equation contexts

Istandardised≈M+NI_{\mathrm{standardised}} \approx M + N

Why this formula appears here

A protocol that both sides target once, instead, lets each side write a single adapter to the shared standard, so the count becomes Istandardised≈M+NI_{\mathrm{standardised}} \approx M + N. This is an illustrative accounting, not a verified cost function — real integrations are not uniform in effort, and a bespoke connector written once is not literally rebuilt M separate times in practice. What the two expressions capture correctly is the shape of the argument both LSP and MCP’s own announcement make: the saving claimed is structural, in how many distinct things must exist and be maintained, not a claim that any single connector becomes individually cheaper to write [ 5 , 6 ] .

Read the full article-specific guide →

Read the representative guide

IstandardisedI_{\mathrm{standardised}}

Symbol I_standardised

IsI_standardised is a part of this expression. Its role is fixed by the surrounding article and by the operations shown in the formula.

Read this term in its guide →
NN

Symbol N

N is a part of this expression. Its role is fixed by the surrounding article and by the operations shown in the formula.

Read this term in its guide →

How to interpret it

Its accuracy depends on the assumptions and range of use described in the article.

Research cited beside this formula

Published contexts (1)

A symbol can carry a different meaning in another article. Each occurrence keeps its own guide and term definitions.

Istandardised≈M+N.I_{\mathrm{standardised}} \approx M + N.

Equation 4 · AI Infrastructure

Function Calling, MCP, and the Other Ways to Give a Model Tools

This equation gives an approximation: it relates the quantities while allowing an approximation.

A protocol that both sides target once, instead, lets each side write a single adapter to the shared standard, so the count becomes Istandardised≈M+NI_{\mathrm{standardised}} \approx M + N. This is an illustrative accounting, not a verified cost function — real integrations are not uniform in effort, and a bespoke connector written once is not literally rebuilt M separate times in practice. What the two expressions capture correctly is the shape of the argument both LSP and MCP’s own announcement make: the saving claimed is structural, in how many distinct things must exist and be maintained, not a claim that any single connector becomes individually cheaper to write [ 5 , 6 ] .

Meanings in this article

  • MM: the number of distinct model-facing client applications.
Equation guide → · Article →