ddg_list_models
List local/free Ollama models and queryable paid/account-backed route labels.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
DDG Agent Services
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It states what is listed but does not disclose any behavioral traits such as authentication requirements, side effects, or performance implications. For a read-only list, this is minimally adequate.
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?
Single sentence with no wasted words. Verb is front-loaded. Efficiently conveys the tool's scope.
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?
Given the tool has no parameters and an output schema exists, the description sufficiently covers what the tool does. Could be slightly improved by noting it is a discovery step before using request/run tools, but is already complete enough for a simple list endpoint.
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?
Tool has zero parameters. Baseline for 0 params is 4. Schema covers all parameters (none), so description adds no parameter information beyond that.
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?
Description uses specific verb 'List' and identifies resources: local/free Ollama models and queryable paid/account-backed route labels. Clearly distinguishes from sibling tools that request or run models.
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 on when to use this tool vs alternatives. Does not mention prerequisites or context, such as that it should be used to discover available models before requesting or running.
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.
TDQS
B3.2/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose, ranging from status checks to order management to payment processing. Despite the large number, descriptions make them easy to differentiate, with no obvious overlap.
Naming Consistency3/5
All tools share the 'ddg_' prefix, but naming patterns vary: some use verb_noun (e.g., ddg_list_models) while others use noun_noun (e.g., ddg_agent_status). This mix reduces consistency, though readability remains acceptable.
Tool Count4/5
With 25 tools, the count is at the high end but scales to cover diverse aspects of payable services (status, orders, payments, models, x402). Minor consolidation could be possible, but most tools earn their place.
Completeness4/5
The tool surface covers core workflows like order lifecycle, payment, and service discovery. Minor gaps (e.g., no cancellation or refund tools) exist but do not severely hinder typical agent interactions.