ddg_list_services
List DDG live/manual services from the public pricing and catalog surfaces.
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
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description must disclose behavioral traits. It only states the tool lists from 'public surfaces,' implying no side effects, but does not mention authentication, rate limits, or whether data is live or cached.
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 the action verb 'List' front-loaded. Entirely concise with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless tool with an output schema, the description is adequate but leaves gaps: it does not define 'live/manual services,' clarify the difference between 'pricing' and 'catalog' surfaces, or explain how this relates to sibling tools.
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?
There are zero parameters, and schema description coverage is 100%. The description adds meaning by explaining what the tool lists, compensating for the lack of parameters.
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 clearly states the tool lists 'DDG live/manual services' from 'public pricing and catalog surfaces,' specifying the verb 'List' and the resource 'services.' It is distinct from sibling list tools like ddg_list_models, but no explicit differentiation is provided.
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 versus alternatives such as ddg_list_models or ddg_list_local_runtime_options. The description lacks context about prerequisites, scenarios, or exclusions.
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.