Skip to main content
Glama
ShadovvSinger

Ollama_MCP_Guidance

simple_chat

Send a single user prompt to an Ollama model and obtain a JSON response with model output and metadata. Ideal for basic question answering without conversation history.

Instructions

Basic chat interaction with Ollama models.

This is a simplified chat implementation that provides basic conversation
capabilities without advanced features. For advanced features, please use
complex_chat (not implemented yet).

Limitations:
1. No conversation history (messages array)
2. No streaming support (stream)
3. No system prompts (system role)
4. No image input support (images)
5. No format control (format)
6. No parameter tuning (options)
7. No keep-alive control (keep_alive)

Features:
1. Basic chat: Single message and response
2. Error handling: Connection and format validation
3. Performance metrics: Processing time and token statistics

Args:
    model (str): Model name to use, e.g., "llama2", "mistral"
    prompt (str): User input text

Returns:
    str: JSON-formatted string containing:
        - Model response and metadata if successful
        - Error details if the request fails or response format is invalid

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYes
promptYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully discloses behavior: no conversation history, no streaming, no system prompts, etc. Also details error handling and performance metrics. The return format is described as JSON with response or error details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections and bullet points, but slightly verbose (repeats 'Basic chat' in two places). Still, every sentence adds information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 params, no nested objects) and the presence of output schema (described in return), the description covers all necessary aspects: purpose, usage, limitations, features, parameters, and return format. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description adds meaning: for 'model', it gives examples like 'llama2', 'mistral'; for 'prompt', it says 'User input text'. This adds value beyond the schema's purely structural definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Basic chat interaction with Ollama models' and distinguishes from 'complex_chat' (though not implemented). The verb 'chat' and resource 'Ollama models' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (basic chat) and when not (advanced features require complex_chat). Lists limitations. However, does not compare to sibling 'simple_generate', which might be another text generation tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ShadovvSinger/Ollama_MCP_Guidance'

If you have feedback or need assistance with the MCP directory API, please join our Discord server