Skip to main content
Glama
ShadovvSinger

Ollama_MCP_Guidance

get_ollama_version

Retrieve the Ollama server version by querying the /api/version endpoint. Use to verify the service is active and obtain version information.

Instructions

Get the version information of the Ollama server.

This tool queries the Ollama API's /api/version endpoint to retrieve the server version.
It's useful for checking if the Ollama service is running and verifying its version.

Args:
    None: This function does not require any parameters.

Returns:
    str: JSON-formatted string containing:
        - Version information if successful
        - Error details if the request fails

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes endpoint (/api/version), that it returns version info or error details. No annotations provided, so description carries burden. Could mention read-only nature, but implied.

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

Conciseness5/5

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

Extremely concise: three short paragraphs with front-loaded summary. No unnecessary information.

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

Completeness4/5

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

Has output schema, description explains return format (JSON string with version or error). Given simplicity, it's complete. Minor oversight: no mention of potential latency or network errors, but acceptable.

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

Parameters5/5

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

No parameters, schema coverage 100%, description explicitly states no args. Perfectly clear.

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?

Clearly states verb (get) and resource (version information of the Ollama server). Distinguishes from sibling tools which are about listing, generating, or chatting, not version retrieval.

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

Usage Guidelines3/5

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

Provides context: 'useful for checking if the Ollama service is running and verifying its version.' No explicit when-not or alternatives, but siblings are clearly different, so sufficient.

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