Azquo

Import file

import_file

Destructive

Import SMALL INLINE DATA into an Azquo database - a base64-encoded blob under fileContent. Filename selects the import template.

THIS IS THE NARROW ROUTE, NOT THE GENERAL ONE. It base64-transports the file through the agent's context, so it is capped at 256 KB and refuses anything larger. Use it ONLY when the data exists solely in your context and you have no shell. Otherwise:

fetchable by URL -> import_from_url. The SERVER downloads it; nothing crosses your context.
you can run curl -> POST /api/importdata with -F 'file=@...' -F 'database=...' and an X-Azquo-Business header if switching business. ~0.1s for a 57 KB file where this tool takes minutes.

See azquo_skills id 813 for the HTTP recipe.

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": {
      "database": "<database>",
      "filename": "<filename>",
      "fileContent": "<fileContent>"
    },
    "name": "import_file"
  }
}

Input Schema

Name	Required	Description
`business`	No	Optional. The business this call is for, by name, e.g. "azquo" - it then runs there whatever business the session is in. Worth giving on writes when you work in more than one business: a new MCP session starts in the login's own business. list_businesses shows the names.
`database`	Yes	Target database name
`filename`	Yes	Original filename including extension — used to select the correct import template
`fileContent`	Yes	Base64-encoded file bytes. Capped at 256 KB decoded - use import_from_url or POST /api/importdata for anything larger.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

addedInput schema / properties / business

Added value: +{
+  "description": "Optional. The business this call is for, by name, e.g. \"azquo\" - it then runs there whatever business the session is in. Worth giving on writes when you work in more than one business: a new MCP session starts in the login's own business. list_businesses shows the names.",
+  "type": "string"
+}

First observedOct 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations carry the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false), and the description adds hard behavioral context beyond them: a 256 KB decode cap that refuses larger input, the fact bytes transit the agent's context, and a concrete performance comparison. It does not say what the import does to existing data in the target database (merge vs overwrite), which is the one behavioral gap left for a destructive write.

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?

Front-loads the narrow-route warning and the cap before the alternative branches, and the bulleted alternatives are easy to scan. Slightly long, with the 256 KB limit repeated in both prose and schema, but every section carries routing or limit information.

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?

Complete enough to call correctly: prerequisites, size cap, template selection, the optional `business` caveat, and escalation paths are all covered, and no output schema exists to require return documentation. The only omission is the effect on pre-existing data in the target database, relevant because the tool is flagged destructive.

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?

Schema description coverage is 100%, so the schema already documents `business`, `database`, `filename` (template selection) and `fileContent` (base64, 256 KB cap). The description largely restates the filename-to-template and content-cap semantics rather than adding syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Import SMALL INLINE DATA into an Azquo database') and immediately scopes it as the narrow route for base64 blobs under `fileContent`. It names the sibling it is not (the general route via import_from_url / HTTP), so an agent can distinguish it without opening the schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('ONLY when the data exists solely in your context and you have no shell') plus two when-not branches with named alternatives: fetchable-by-URL to import_from_url and shell-available to POST /api/importdata. It even quantifies the tradeoff (~0.1s vs minutes).

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

All Azquo 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?