Antevo Mandates

Add a document (not available yet)

upload_document

Read-onlyIdempotent

Adding a document is not available over this connector yet. Returns the ways to add one — the Antevo app's Vault, or the REST upload flow. Nothing is stored and no record is created; the other arguments are accepted but not used.

Input Schema

Name	Required	Description	Default
`domain`	No
`confirm`	No
`category`	No
`file_name`	No
`description`	No
`household_id`	No
`base64_content`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 27, 2026
- addedInput schema / properties / category / default
```
Added value: +""
```
- addedInput schema / properties / domain / default
```
Added value: +""
```
- addedInput schema / properties / file_name / default
```
Added value: +""
```
- addedInput schema / properties / household_id / default
```
Added value: +""
```
- removedInput schema / required
```
Removed value: -[
-  "household_id",
-  "file_name",
-  "domain",
-  "category"
-]
```
First observedOct 18, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description goes beyond the annotations by disclosing that 'Nothing is stored and no record is created' and that the other arguments are 'accepted but not used' — key operational facts the annotations alone don't convey. However, annotations already carry readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the description's incremental safety contribution is by definition limited (no auth, rate-limit, or error behavior is described).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the critical fact front-loaded ('not available over this connector yet'), and no filler. The last clause about unused arguments is essential context. It is sized appropriately for a stub tool and earns its place.

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?

For a stub/guidance tool with an output schema present, the description supplies everything needed: the tool is not functional, nothing persists, arguments are ignored, and the real paths are named. No gaps that would cause a mis-call.

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?

With 7 parameters and 0% schema description coverage, the description must compensate — and it does so in the most useful possible way by declaring that every argument besides the implied ones is inert ('accepted but not used'). It doesn't define individual fields like household_id or base64_content, but their semantics are moot given the tool never acts on them.

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 immediately corrects the misleading name: this tool does not upload anything, it 'Returns the ways to add one' (the Antevo Vault or the REST upload flow). That is a specific, unambiguous statement of what the call actually does, and it implicitly steers the agent away from expecting a real document write.

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

Usage Guidelines4/5

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

It states plainly that uploading is not possible here and names the two real alternatives (in-app Vault, REST upload), which is exactly the routing information an agent needs. It does not name sibling tools explicitly, so it stops just short of a full when/when-not table.

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

All Antevo Mandates 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.