The server
What a caller can ask it, and where each answer comes from.
What a client gets at initialize and in the lists it fetches right
after: the result as the server sends it, the instructions in their
wording, the prompts, and what the tool list weighs.
Every tool, one page each. What it is for, what it takes, which fields it answers with, and what one call to it came back with.
The other surface a client gets, the one a user picks out of a list rather than calls mid-task.
The five sources an answer can come from, and what each one needs up before it can.
What ships in knowledge/, which is where almost every answer comes
from.
How a statement that holds for some TYPO3 versions and not others says so, and why a catalog withholds an entry instead of a qualification.
The order the server looks an installation's own answers up in, how it delivers the probe, and what a fallback owes the caller.
A community proposal for an MCP interface contract for TYPO3, read as a reference. What it says, and what would change here if the community adopted it.
What a client gets at initialize and in the lists it fetches right
after: the result as the server sends it, the instructions in their
wording, the prompts, and what the tool list weighs.
What a client gets at initialize
What a client gets at initialize and in the lists it fetches right
after: the result as the server sends it, the instructions in their
wording, the prompts, and what the tool list weighs.
Every tool, one page each. What it is for, what it takes, which fields it answers with, and what one call to it came back with.
Tools
Every tool, one page each. What it is for, what it takes, which fields it answers with, and what one call to it came back with.
The other surface a client gets, the one a user picks out of a list rather than calls mid-task.
Resources
The other surface a client gets, the one a user picks out of a list rather than calls mid-task.
The five sources an answer can come from, and what each one needs up before it can.
Where an answer comes from
The five sources an answer can come from, and what each one needs up before it can.
What ships in knowledge/, which is where almost every answer comes
from.
The bundled knowledge
What ships in knowledge/, which is where almost every answer comes
from.
How a statement that holds for some TYPO3 versions and not others says so, and why a catalog withholds an entry instead of a qualification.
Which versions an answer holds for
How a statement that holds for some TYPO3 versions and not others says so, and why a catalog withholds an entry instead of a qualification.
The order the server looks an installation's own answers up in, how it delivers the probe, and what a fallback owes the caller.
Asking the installation
The order the server looks an installation's own answers up in, how it delivers the probe, and what a fallback owes the caller.
A community proposal for an MCP interface contract for TYPO3, read as a reference. What it says, and what would change here if the community adopted it.
The draft RFC on an MCP interface contract for TYPO3
A community proposal for an MCP interface contract for TYPO3, read as a reference. What it says, and what would change here if the community adopted it.
The tools are the server. Everything else on this page is either the other surface beside them or an account of where their answers come from. That is the one thing a caller cannot see from a tool's own description. It is the reason every answer names its source, its version bound and what it left out.