Skip to main content
Glama
yunwuneo

AxonHub MCP Server

by yunwuneo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List AxonHub models

axonhub_list_models

Lists configured models in AxonHub with capabilities, costs, limits, and channel counts. Use pagination and filters to inspect model inventory and compare resource allocation.

Instructions

List configured models, capabilities, costs, limits, and associated channel counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoPagination cursor returned by a previous call.
firstNo
whereNoOptional ModelWhereInput filter.
projectIdNoAxonHub project ID. Uses AXONHUB_PROJECT_ID when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The verb 'List' indicates a read-only operation, and no side effects are described. With no annotations provided, the description sufficiently conveys that this tool does not modify state, though it could be more explicit about being safe.

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, direct sentence that lists the key elements without unnecessary elaboration. It is concise and well-structured.

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 simple listing tool, the description provides sufficient context about the purpose and data returned. It does not specify the output format, but this is not critical for a list operation, and sibling context is not needed to understand its role.

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

Parameters3/5

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

The schema includes descriptions for three of four parameters (after, where, projectId), but 'first' lacks a description. The tool description does not add further parameter details, leaving the schema to carry the meaning for most parameters.

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 'List' and the resource 'models', and specifies the included details (capabilities, costs, limits, channel counts). This makes the purpose unambiguous and distinct from sibling tools.

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 explicit guidance is provided on when to use this tool versus alternative listing tools. The description implies usage for listing models but does not mention any conditions or contrast with siblings like list_projects or list_channels.

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