llm-echo
Debug plugin for LLM. Adds a model which echos its input without hitting an API or executing a local LLM.
Installation
Install this plugin in the same environment as LLM.
llm install llm-echo
Usage
The plugin adds a echo model which simply echos the prompt details back to you as JSON.
llm -m echo prompt -s 'system prompt'
Output:
{
"prompt": "prompt",
"system": "system prompt",
"attachments": [],
"stream": true,
"previous": []
}
You can also add one example option like this:
llm -m echo prompt -o example_bool 1
Output:
{
"prompt": "prompt",
"system": "",
"attachments": [],
"stream": true,
"previous": [],
"options": {
"example_bool": true
}
}
Tool calling
You can use llm-echo to test tool calling without needing to run prompts through an actual LLM. In your prompt, send something like this:
{
"prompt": "This will be treated as the prompt",
"tool_calls": [
{
"name": "example",
"arguments": {
"input": "Hello, world!"
}
}
]
}
You can assemble a test that looks like this:
def example(input: str) -> str:
return f"Example output for {input}"
model = llm.get_model("echo")
chain_response = model.chain(
json.dumps(
{
"tool_calls": [
{
"name": "example",
"arguments": {"input": "test"},
}
],
"prompt": "prompt",
}
),
system="system",
tools=[example],
)
responses = list(chain_response.responses())
tool_calls = responses[0].tool_calls()
assert tool_calls == [
llm.ToolCall(name="example", arguments={"input": "test"}, tool_call_id=None)
]
assert responses[1].prompt.tool_results == [
llm.models.ToolResult(
name="example", output="Example output for test", tool_call_id=None
)
]
Or you can read the JSON from the last response in the chain:
response_info = json.loads(responses[-1].text())
And run assertions against the "tool_results" key, which should look something like this:
{
"prompt": "",
"system": "",
"...": "...",
"tool_results": [
{
"name": "example",
"output": "Example output for test",
"tool_call_id": null
}
]
}
Take a look at the test suite for llm-tools-simpleeval for an example of how to write tests against tools.
echo-needs-key model
The plugin also provides an echo-needs-key model which behaves identically to echo but requires an API key. This is useful for testing key resolution logic in plugins like datasette-llm.
The resolved key is included in the JSON output:
LLM_ECHO_NEEDS_KEY_KEY=sk-test-123 llm -m echo-needs-key 'hello'
Output:
{
"prompt": "hello",
"system": "",
"attachments": [],
"stream": true,
"previous": [],
"key": "sk-test-123"
}
The model's needs_key is "echo-needs-key" and its key_env_var is LLM_ECHO_NEEDS_KEY_KEY.
Raw responses
Sometimes it can be useful to output an exact string, for example if you are testing the --extract option in LLM.
If your prompt is JSON with a "raw" key that string is the only thing that will be returned. For example:
{
"raw": "This is the raw response"
}
Will return:
This is the raw response
Development
To set up this plugin locally, first checkout the code. Then run the tests:
cd llm-echo
uv run pytest
Release files for llm-echo 0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| llm_echo-0.4.tar.gz | 8.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llm_echo-0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.2 kB
Release files / llm_echo-0.4.tar.gz
| Download URL | llm_echo-0.4.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10f9fa0e57ebc995d0a39f88c9972238760ac6d86501062ae9eeee75ec838bba
|
|
BLAKE2b-256 checksum How to use checksums |
c854c103996593deaebed71b24fbae789ed0b094215b5d5e1eba4227d7a1ac49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 31, 2026.
Transparency logRelease files / llm_echo-0.4-py3-none-any.whl
| Download URL | llm_echo-0.4-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b4b5865eae88f4a987bfb6ead487d6f14389fa0ff81b16b23526e5e0a6cc29ca
|
|
BLAKE2b-256 checksum How to use checksums |
f6aa26c3e00e5240bba3c603c90cb4ae5655d2015e706653f553e7e897316171
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 31, 2026.
Transparency log