Skip to main content
Glama
Sign In
timeweb-mcp-server

timeweb-mcp-server

by webkoth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

timeweb_list_database_backups

Retrieve all backups for a specific database cluster using its unique ID. Control result count and output format.

Instructions

List all backups for a database cluster

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "db_id": "<db_id>"
    },
    "name": "timeweb_list_database_backups"
  }
}

Input Schema

NameRequiredDescriptionDefault
db_idYesDatabase cluster ID
limitNoMaximum number of results to return (1-100)
formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readable
offsetNoNumber of results to skip for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'List all backups', which implies a read operation but does not mention pagination behavior (despite limit/offset parameters), whether manual and automatic backups are included, or response structure. This is insufficient for a tool with untrusted behavior.

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 concise sentence that directly states the purpose with no filler or redundancy. It is front-loaded and efficient, earning a top score for conciseness.

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

Completeness2/5

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

For a list operation with no output schema, the description should explain return values or pagination to be complete. It does not mention that 'all backups' may be paginated via limit/offset, nor does it clarify what fields are returned. The minimalism leaves significant gaps in context for an agent.

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 input schema provides complete descriptions for all four parameters (db_id, limit, format, offset), covering 100% of the schema. The description itself adds no extra parameter semantics, so the baseline score of 3 is appropriate.

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's function: 'List all backups for a database cluster' with a specific verb ('List') and resource ('backups for a database cluster'). It is unambiguous and distinct from sibling tools like create/delete backup, though it does not explicitly differentiate itself from related tools such as get_database_auto_backups.

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 is provided on when to use this tool versus alternatives like creating or deleting backups, or when to use auto-backup settings. The description offers no context for decision-making, leaving the agent to infer usage from the name alone.

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