Skip to main content
Glama

get_model_info

Obtain detailed information about a specific Ollama model, including configuration and metadata, to support local model management and inference without cloud dependencies.

Instructions

Get detailed information about a specific Ollama model.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
model_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'get_model_info'. Registered with @mcp.tool decorator, delegates to oc.get_model_info and truncates the modelfile to 500 chars.
    @mcp.tool(
        name="get_model_info",
        description="Get detailed information about a specific Ollama model.",
    )
    async def get_model_info(model_name: str) -> dict[str, Any]:
        """
        Args:
            model_name: The name of the model (e.g. 'llama3', 'mistral:7b').
        """
        info = await oc.get_model_info(model_name)
        # Trim the modelfile to avoid huge outputs
        modelfile = info.get("modelfile", "")
        if len(modelfile) > 500:
            info["modelfile"] = modelfile[:500] + "..."
        return info
  • The @mcp.tool decorator registers 'get_model_info' as an MCP tool with FastMCP.
    @mcp.tool(
        name="get_model_info",
        description="Get detailed information about a specific Ollama model.",
    )
  • The underlying async helper function that calls the Ollama API (POST /api/show) to fetch model info.
    async def get_model_info(name: str) -> dict[str, Any]:
        async with _client() as c:
            r = await c.post("/api/show", json={"name": name})
            r.raise_for_status()
            return r.json()
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'Get detailed information' without disclosing the return format, side effects, or that it is read-only. This is minimal behavioral disclosure for a read operation.

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?

The description is a single, efficient sentence with no unnecessary words. It earns its place by clearly stating the tool's purpose.

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

Completeness3/5

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

Given the simplicity of the tool (single required parameter) and the presence of an output schema, the description is minimally adequate. However, it lacks behavioral transparency and parameter guidance, making it less than ideal for an agent.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the model_name parameter beyond the schema. No guidance on valid values or format is provided, leaving the agent with no additional semantic information.

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 the action ('Get') and resource ('detailed information about a specific Ollama model'). It distinguishes from sibling tools like list_models (which lists all) and delete_model (different action).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as list_models or list_running_models. The description does not specify exclusions or prerequisites.

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/deadSwank001/Nexus-MCP'

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