Skip to main content
Glama
Sign In
pi-connector-cc

pi-connector-cc

by agamairi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

pi_models

List Ollama models available on a specific endpoint or host, or across all configured endpoints to check which models are ready for coding agent jobs.

Instructions

List Ollama models for one endpoint, host, or all configured endpoints.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pi_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNo
modelNo
endpointNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It never states that this is a read-only/network-contacting operation, what happens if an endpoint is unreachable or misconfigured, or whether the call is scoped to local vs remote hosts — all material for a tool that reaches out to endpoints.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity contributes to the gaps in parameter and behavioral detail rather than being a model of tight, complete writing.

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

Completeness2/5

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

No annotations, no output schema, and 0% parameter coverage mean the description is the only source of truth, and it leaves the host-vs-endpoint distinction, the model filter, and failure behavior unexplained. For a three-parameter discovery tool the definition is under-specified.

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

Parameters2/5

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

Schema coverage is 0%, so the description must explain the three parameters, but it only gestures at host/endpoint without clarifying how they differ or what happens when both are supplied. The "model" parameter is never mentioned at all, leaving it completely ambiguous — especially odd for a listing tool.

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

Purpose4/5

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

The description gives a specific verb and resource ("List Ollama models") and states the scope variants ("one endpoint, host, or all configured endpoints"). It is clear what the tool does, though it never contrasts itself with the similar-sounding sibling pi_list, so an agent must infer the boundary.

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?

The phrase "for one endpoint, host, or all configured endpoints" hints at invocation variants but gives no when-to-use/when-not guidance, no prerequisites (e.g. whether Ollama must be configured first), and no mention of pi_list or pi_configure as alternatives.

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

Deploy Server

Other Tools