Skip to main content
Glama
colecantu904

virtuous-mcp

by colecantu904

create_batch

Submit bulk imports of contacts or gifts to run through matching, validation, and deduplication, reducing API calls by batching.

Instructions

MUTATING: submit a BULK import of contacts or gifts (the rate-limit-friendly, Virtuous-recommended way to load many records at once).

Virtuous best practices say: to load many gifts/contacts, post them through the BATCH endpoints rather than one transaction per call. This both runs the records through Virtuous's matching/validation/dedupe pipeline AND makes far fewer requests against the ORG-WIDE rate budget (one batch call instead of N).

'contact' -> POST /api/Contact/Batch 'gift' -> POST /api/v2/Gift/Transactions DO NOT call with confirm=true unless the user explicitly approved it. With confirm=false this performs no change and returns a preview (including how many records are in the batch).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesBulk payload. For 'gift' this is typically a list of gift transaction objects (same shape as a single gift transaction). For 'contact' this is the contact-import batch payload. Use describe_endpoint on the target path for the exact schema.
kindYes'contact' or 'gift' — which bulk import to submit.
confirmNoMust be true to actually submit. Set ONLY after explicit user approval.
Behavior5/5

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

Discloses mutation, rate-limit benefits, preview behavior on confirm=false, and the need for user approval for confirm=true, compensating for absent annotations.

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?

Front-loaded with 'MUTATING' and clear purpose; every sentence adds value despite length, with no redundant phrases.

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

Completeness5/5

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

Covers all aspects needed given no output schema: explains preview on confirm=false, validates behavior, and references best practices, making it fully actionable.

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

Parameters5/5

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

Adds meaning beyond schema: explains body references describe_endpoint for exact schema, kind lists 'contact' or 'gift', and confirm must be set only after user approval.

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?

Description explicitly states it submits bulk imports of contacts or gifts, specifying 'BULK import' and distinguishing from single-record tools like create_record and create_transaction.

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?

Clearly states when to use (loading many records), mentions it's rate-limit-friendly and Virtuous-recommended, and warns against calling with confirm=true without explicit approval.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/colecantu904/virtuous-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server