Loading ToolBench
MCP server for Alibaba Cloud ApsaraDB for MongoDB, providing tools for MongoDB instance management, database operations, and VPC/network configuration
Server has 8 tools with basic schemas and descriptions, but significant gaps limit production readiness. All tools have descriptions (10-200 chars, mostly adequate), and input schemas are present with type definitions. However, output schemas are undocumented (tools return raw API responses or unstructured strings), parameter descriptions lack constraint details (enums, ranges, formats), and error handling is minimal. No tool annotations (readOnlyHint, destructiveHint). Naming is verb-noun compliant but generic (describe_*, list_*). Security concern: connection_string exposed as parameter in MongoDB tools, risking credential leakage into logs.
Query available resource(instance class) for MongoDB instances.
Query available zones for MongoDB instances.
Query detailed information about a specific MongoDB instance.
Queries all MongoDB instances in a region.
Query VPC list.
Query VSwitch list.
Connection strings exposed as tool parameters in list_databases and get_top_reusable_space_collections. Credentials will leak into agent logs and prompt history. Must use server-side secret injection via environment variables.
Output schemas completely undocumented. Tools return raw API response dicts or unstructured strings (e.g., 'Failed to list databases, exception: ...'). LLMs cannot plan downstream calls or extract structured data. Must document return types with field names and types.
Parameter descriptions lack constraint details. 'instance_charge_type' lists values in description text ('PrePaid', 'PostPaid') but not as enum schema. 'engine_version' and 'replication_factor' similarly lack formal constraints. Enums prevent hallucinated values and are machine-parseable.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | <=2025-11-25 | v2 |
Get the top N collections with the most reusable space in a MongoDB instance.
Query the size of all databases in a MongoDB instance.
Error handling returns raw exception strings ('Failed to list databases, exception: ...') with no recovery guidance. LLMs cannot determine if error is retryable, user-fixable, or fatal. Must categorize errors and suggest next steps.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). All tools are read-only but this is not declared in schema. Agents cannot distinguish safe tools from destructive ones without explicit hints.