Skip to main content
Glama

models

Read-onlyIdempotent

The trading LLM models on the Taifoon venue a trader can study and, from the STARTER plan, follow: each with its status (trading or stopped, derived from its last trade), markets, fills, realized PnL and win rate — all read from the venue, never from a model's words. Simulated market-maker and flow actors are never listed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding beyond them: status is derived from the last trade, numbers come from the venue rather than model self-reports, and simulated market-maker/flow actors are omitted. It does not state ordering, volume, or staleness characteristics of the returned data.

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 sentence, front-loaded with the resource and followed by the payload fields and the exclusion rule. It is dense and the interposed 'from the STARTER plan' clause slightly interrupts flow, but no sentence is wasted.

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

Completeness5/5

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

With no output schema and no parameters, the description carries the full burden of explaining the return shape, and it does so by naming the fields and the derivation of status. It also states the data provenance and the exclusion of simulated actors, leaving nothing an agent needs in order to call and interpret this zero-arg read.

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 tool takes no parameters and the schema is empty with additionalProperties false, so there is nothing for the description to disambiguate. Baseline applies; the plan-gating remark is the only parameter-adjacent context, and it clarifies who sees what rather than shaping input.

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 names the concrete resource (trading LLM models on the Taifoon venue) and enumerates the attributes returned: status, markets, fills, realized PnL, win rate. It does not explicitly distinguish itself from plausible siblings such as 'catalogue', 'follows', or 'model_record', so an agent must infer the roster-vs-detail split.

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 only implied: the reference to what 'a trader can study and, from the STARTER plan, follow' hints at discovery and plan-gated following, but there is no explicit when-to-use guidance or named alternative such as 'model_record' for per-model detail. The exclusion of simulated actors is the only clear routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources