Skip to main content
Glama

mercoa

by io.usefulapi

Create entity

mercoa_create_entity
Destructive

WRITE — creates a real entity (customer/vendor/payor/payee) in Mercoa. Supply role flags, accountType, and a nested profile object (business or individual details). POST /entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoPrimary email for the entity.
isPayeeNoWhether this entity can receive payments (AR / vendor).
isPayorNoWhether this entity can pay invoices (AP).
profileNoNested profile object, e.g. { "business": { "legalBusinessName": "Acme Inc.", "email": "ap@acme.com", "businessType": "llc" } } or { "individual": { "name": {...}, "email": "..." } }.
foreignIdNoYour system's ID for this entity.
isCustomerNoWhether this entity has a direct relationship with your organization.
accountTypeNobusiness or individual.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotation 'destructiveHint: true' indicates mutation, and the description reinforces this with 'WRITE' and 'creates'. It adds behavioral context by detailing the resource type and key inputs, though it omits side effects or authentication requirements.

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 20-word sentence that front-loads the purpose with 'WRITE — creates a real entity'. Every word earns its place, with no redundancy.

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

Completeness3/5

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

For a tool with 7 parameters, nested objects, and no output schema, the description covers the core purpose but lacks details on constraints (e.g., foreignId uniqueness), parameter relationships, and the response format. The schema compensates partially.

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 already provides 100% coverage with descriptions for all 7 parameters. The description summarizes key groups ('role flags, accountType, profile') but does not add significant new meaning beyond the schema.

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?

The description clearly states 'creates a real entity (customer/vendor/payor/payee) in Mercoa', specifying the action (create), resource (entity), and example roles. It distinguishes from sibling tools like 'mercoa_get_entity' by focusing on creation.

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?

The description provides clear usage context by specifying required inputs: 'Supply role flags, accountType, and a nested `profile` object'. It does not explicitly mention when not to use this tool or alternatives, but the context is clear for a creation tool.

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

All mercoa toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct resource (entity, invoice, transaction, payment method, organization) and action (create, find, get, list, update, add). There is no ambiguity between tools.

Naming Consistency5/5

All tools follow the consistent pattern 'mercoa_verb_noun' using snake_case. Verbs like create, find, get, list, update are used predictably.

Tool Count5/5

With 17 tools covering entities, invoices, transactions, payment methods, and organization, the count is well-scoped for a financial platform. Each tool justifies its existence.

Completeness4/5

The toolset covers core CRUD and query operations for the main resources. Minor gaps exist such as missing delete operations for entities and invoices, but the surface is largely complete for typical workflows.

Resources