Spiral gives your agent every tool with one account. Browse the tools →

Manus · Developer

How to Use Ollama model details in Manus

Returns a model's description, capabilities, and README from Ollama. Use it to understand the model's intended tasks before checking a specific tag's size or layer metadata.

Prompts to try with Ollama model details in Manus

Copy an example into Manus, or ask in your own words.

Use Ollama model details for qwen3-embedding and summarize the retrieval tasks described in its README.

Ollama model detailsManus
Try asking
  • Use Ollama model details to look this up and give me the result as a table.

  • Pull the latest numbers from Ollama model details and tell me what changed since last week.

  • Check Ollama model details and summarize what you find in three bullet points.

  • Pull the newest data from Ollama model details and give me the result as a table.

How to set up Ollama model details in Manus

Pick the way that suits you. Each takes about two minutes.

Use the Manus connector

  1. Add a custom MCP connector

    In Manus open Settings › Connectors (or the connectors icon under the chat box), then Add connectors › Custom MCP and Add MCP by URL. Name it Spiral, set Transport to HTTP and paste this Server URL:

    https://api.spiral.ai/mcp
  2. Sign in to Spiral and approve

    Manus asks you to sign in the first time it uses Spiral. Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Manus never sees it, and you can remove it under Settings › Connected apps in the console.

Use the Spiral skill

  1. Send Manus this message

    Your agent reads Spiral's skill and sets itself up.

    set up https://spiral.ai/SKILL.md
  2. Sign in or paste a key

    Approve Spiral in the browser, or give the agent a key from the console.

Use the Spiral CLI

  1. 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

  1. Create an API key

    In the console, under API keys.

  2. Run Ollama model details

    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/model",
        "input": {
          "model": "<model>"
        }
      }'

Then paste one of the prompts above: Manus finds Ollama model details on Spiral, shows the price and runs it.

Ollama model details providers and prices

Spiral runs Ollama model details through Alexandria. Open a card for today's price, with every fee included.

AlexandriaDeveloper
Ollama model library · Model
ollama-com/models/model

What can you do with Ollama model details in Manus?

Get an Ollama model comparison that explains which builds deserve a closer look for document search or coding. A chat app can turn catalog descriptions, tag sizes, and layer metadata into a readable selection brief.

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.

Follow a public model publisher

Compare a publisher's current catalog with earlier results, read descriptions for newly seen models, and inspect their available tags. Produce a review list of uploads relevant to embedding or coding work.

Questions about Ollama model details in Manus

Can Manus use Ollama model details?

Yes. Add Spiral to Manus as an MCP server, and Manus can find and run Ollama model details like any built-in tool.

How much does Ollama model details cost in Manus?

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Manus plan is separate.

Do I need an Alexandria account to use Ollama model details in Manus?

No. Spiral runs Ollama model details 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 details in Manus?

About two minutes: add a custom MCP connector, then sign in to Spiral and approve.

Does Manus wait while Ollama model details runs?

Ollama model details runs in the background. Manus 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.

Get started

Start using Ollama model details in Manus

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Manus:

Set up Manus

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options