solanaprox-mcp

list_models

Fetches the models SolanaProx serves now, with live prices per 1M tokens and tool support, so you can choose a model without a token or account.

Instructions

List the models SolanaProx serves right now, with live prices per 1M tokens and tool support (GET /v1/models). Free, and needs no token.

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": "list_models"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.0Nov 7, 2026
- removedInput schema / required
```
Removed value: -[]
```
First observedv1.0.0Mar 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does address the two traits that matter most here: cost ('Free') and authentication ('needs no token'), both of which an agent would otherwise have to guess. It also signals liveness ('right now'), though it says nothing about rate limits or response ordering.

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?

A single sentence that front-loads the resource, then the payload contents, then the zero-cost/zero-auth property. Nothing is repeated and every clause carries information an agent needs.

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?

For a zero-parameter read-only catalog call with no output schema, the description supplies the return contents (models, prices per 1M tokens, tool support) and the access constraints. The only omission is the shape or ordering of the returned list, which is minor for a tool this simple.

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?

The schema has zero properties, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly implies a no-argument call by mentioning only the endpoint.

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 states a specific verb and resource ('List the models SolanaProx serves') and immediately enumerates what each entry contains: live prices per 1M tokens and tool support. The canonical endpoint (GET /v1/models) further pins down the operation, and the resource is clearly distinct from siblings like ask_ai or check_balance.

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?

Usage is implied rather than stated: an agent can infer this is the discovery call to make before invoking ask_ai, but the description never says so explicitly and names no alternatives or exclusions. The 'free, needs no token' note gives a practical precondition but not selection guidance.

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

Deploy Server