ParseHub.dev (documents to records)

export_database

Copy data from one configured database to another. Administrators only.

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": {
      "source_db": "<source_db>",
      "target_db": "<target_db>"
    },
    "name": "export_database"
  }
}

Input Schema

Name	Required	Description	Default
`source_db`	Yes
`target_db`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses that the caller must be an administrator and that data moves between two 'configured' databases, but says nothing about whether the target is overwritten or appended, whether the copy is synchronous, how long it takes, or what happens on failure — critical gaps for a mutation tool.

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?

Two short sentences with the action front-loaded and no filler. However, the brevity tips into under-specification rather than true efficiency for a mutation tool with two mandatory parameters.

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?

With no annotations, no output schema, and 0% schema description coverage, the definition omits essentials: what is returned on success, whether the target is overwritten, and how to interpret the two database parameters. The admin note is the only behavioral detail provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate for both parameters. It only hints that the databases must already be 'configured' and that they are directional (source vs target); it gives no naming format, no indication of whether values are identifiers or display names, and no constraints on valid pairings.

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?

States a specific verb and resource: 'Copy data from one configured database to another,' which makes the source→target semantics clear. It does not differentiate from siblings like database_status or get_database_document, and 'copy' slightly conflicts with the tool name 'export', but the core action is unambiguous.

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?

'Administrators only' states an authorization prerequisite but gives no guidance on when to choose this tool over database_status or the document tools, no conditions under which it should not be used, and no mention of alternatives.

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

All ParseHub.dev (documents to records) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?