CypherMonkeyAI omni-channel lab

A lifelong-learner lab on AI omni-channel agents, including voice and the contact center. Free to read. Nothing sold.

Model Context Protocol · L2 · 20 min

Tools, resources, and prompts

Learn in five minutes

  • A tool does something and returns a result.
  • A resource is data the server can show, like a note.
  • A prompt is a template the server offers.
  • Confirm the current spec's exact names before you code.
  • Mixing the three in one function makes the consent screen unclear.

Reading a note is a resource. Sending a message is a tool with a side effect. The consent copy should say which one the person is allowing.

This section HTML

Visual

T6-R3 diagram

Diagram SVGDiagram PNGDiagram HTML

Flow SVGFlow PNGFlow HTML

Label three operations

  1. List notes: resource.
  2. Read one note: resource.
  3. Send a summary: tool, because it leaves the machine.
  4. Write the consent line for the tool only.

This section HTML

Quiz

Which operation is a side effect?

Sending leaves the machine.

Why separate the three?

The person should see what they allow.

What should you do before coding names?

Names in the spec can be revised.

This section HTML

Ecosystem

Resource
Data a server can expose without necessarily changing the outside world.

Sisters: Plugins, Function calling, Language-server ideas.

A notes server can serve chat and a voice host if both speak the same protocol.

Treat the spec revision as something you pin, like a model id.

Config

  • Write the goal in one sentence.
  • Name the input and the allowed output.
  • Save the trace next to the result.

Troubleshooting

  • The answer looks fluent and is wrong. Check whether a source passage actually contains the claim.
  • The loop never stops. Set a step cap and stop when the tool result repeats.

This section HTML

Sources HTML

Sources and go deeper

sources.json