How to Use Ollama model layer metadata in Cline
Returns a model layer's architecture, context length, embedding dimensions, and tensor metadata. Use it to check the actual build before choosing an embedding model or comparing quantization.
Prompts to try with Ollama model layer metadata in Cline
Copy an example into Cline, or ask in your own words.
Use Ollama model layer metadata to inspect qwen3-embedding:0.6b, then compare its embedding dimension and context length with the assumptions in this project's retrieval code.
Use Ollama model layer metadata to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from Ollama model layer metadata and tell me what changed since last week.
Check Ollama model layer metadata and summarize what you find in three bullet points.
Pull the newest data from Ollama model layer metadata and give me the result as a table.
How to set up Ollama model layer metadata in Cline
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the server
In the Cline panel, click the MCP Servers icon and open the Remote Servers tab. Enter:
cline mcp add spiral https://api.spiral.ai/mcp --transport http --yes
- Sign in
Open the Configure tab and click Authenticate on the Spiral server. Sign in to Spiral, pick the organization and click Authorize. No API key.
- Check it
Spiral shows as connected on the Configure tab. In the CLI:
cline config mcp
Use the Spiral skill
- Send Cline this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run Ollama model layer metadata
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "ollama-com/models/layer_metadata", "input": { "tag": "<tag>", "model": "<model>", "layer_digest": "<layer_digest>" } }'
Then paste one of the prompts above: Cline finds Ollama model layer metadata on Spiral, shows the price and runs it.
Ollama model layer metadata providers and prices
Spiral runs Ollama model layer metadata through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Cline for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Include tensors | on or off | Return the tensor table (name, type, shape); a few hundred rows. Default false. |
Every API field of Ollama model library · Layer metadata is on its tool page: open its card above.
What can you do with Ollama model layer metadata in Cline?
Build a model selection report that connects your project's requirements to Ollama descriptions, tags, and layer metadata. A coding agent can compare those results with the embedding dimensions or model references already in your code.
Choose an embedding model for document search
Find official and community candidates, review a publisher's uploads, and read model descriptions. Compare tags, download contents, context lengths, and embedding dimensions before choosing a build for a retrieval trial.
Prepare a coding-model evaluation
Collect candidates from the library, search results, and selected publishers. Read their stated tasks, compare available builds, and inspect tag contents and tensor types to define which exact models to benchmark.
Plan model downloads for an offline deployment
Build a shortlist from official listings and public publisher catalogs, then review model descriptions and tags. Use manifest sizes and layer metadata to document the selected downloads, architecture, and quantization.
Write a technical model comparison
Compare models discovered through the official library, search, and publisher pages. Support the report with README descriptions, tag choices, download sizes, layer identifiers, and metadata from the selected builds.
Check an embedding migration
Compare nomic-embed-text and qwen3-embedding builds using their model descriptions, tags, layers, context lengths, and embedding dimensions. Identify differences to account for before testing a replacement search index.
Inspect mixed tensor quantization
Choose a llama3.2 tag, identify its model layer, and examine individual tensor types and shapes. Explain where the tensor table contains types such as Q4_K, Q6_K, and F32.
More on Ollama model layer metadata and Cline
Overview
Ollama model layer metadata in other agents
Questions about Ollama model layer metadata in Cline
Can Cline use Ollama model layer metadata?
Yes. Add Spiral to Cline as an MCP server, and Cline can find and run Ollama model layer metadata like any built-in tool.
How much does Ollama model layer metadata cost in Cline?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Cline plan is separate.
Do I need an Alexandria account to use Ollama model layer metadata in Cline?
No. Spiral runs Ollama model layer metadata on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up Ollama model layer metadata in Cline?
About two minutes: add the server, then sign in, then check it.
Does Cline wait while Ollama model layer metadata runs?
Ollama model layer metadata runs in the background. Cline starts the run, checks on it and gives you the json when it's ready.
Does Ollama include community uploads?
Yes. Ollama has public publisher namespaces as well as its official library. For example, aiconjured's catalog includes Qwen3-Embedding-0.6B-Q8-NVFP4.
How many builds can one model have?
The count depends on the model. The inspected llama3.2 page lists 63 tags across choices that include 1B and 3B models, so a model name alone does not identify one download.
How does Ollama show how recently a model changed?
Catalog and tag entries display relative update ages. For example, the inspected llama3.2:1b tag shows “2 years ago” beside its size and context information.
Where can I check an embedding build's context length and dimensions?
Ollama's model layer metadata provides both. The inspected nomic-embed-text layer reports a context length of 2,048 and an embedding length of 768.
Can every model in Ollama's catalog answer chat questions?
No. For example, nomic-embed-text is explicitly limited to generating embeddings, so use its catalog data to evaluate search or retrieval models.
Start using Ollama model layer metadata in Cline
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Cline:
set up https://spiral.ai/SKILL.md


