How does discovery differ between traditional APIs and MCP?
Traditional APIs rely on static external documentation (OpenAPI specs or developer portals) parsed by human engineers. MCP clients discover capabilities dynamically at session startup through JSON-RPC list queries (`tools/list`, `resources/list`).
Answered in
MCP vs Traditional APIs: Dynamic Self-Discovery and Capability Contracts for AI AgentsHow Anthropic's Model Context Protocol compares to REST and gRPC, why AI clients require runtime self-describing schemas, and when each protocol fits.
Read the full analysisOther questions this article answers
More how ai actually works questions
- What distinguishes a Deep Research agent from standard retrieval-augmented generation (RAG)?
- How do orchestrator agents coordinate parallel research workers?
- Why do Deep Research systems employ a separate citation agent during synthesis?
- What is the key difference between OpenAI and Gemini planning approaches?
- Why did a simple OCR plus LLM pipeline fail on real-world menus?
- What is the role of the guardrail classifier in the ingestion pipeline?
- Why did LightGBM outperform deep neural networks like ViT and ResNet for guardrailing?
- How do multimodal LLMs complement traditional OCR extraction pipelines?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the How AI Actually Works beat.