Skip to main content
Glama
advenimus

SyncroMSP MCP Server

payments_create

Record a payment for a customer and optionally distribute it across multiple invoices using invoice IDs and amounts.

Instructions

Record a payment. Use apply_payments to distribute a payment across multiple invoices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYesCustomer ID (required)
invoice_idNoInvoice ID
invoice_numberNoInvoice number
amount_centsNoAmount in cents
payment_methodNoPayment method
ref_numNoReference number
address_streetNoBilling street
address_cityNoBilling city
address_zipNoBilling ZIP
register_idNoRegister ID
signature_nameNoSignature name
apply_paymentsNoObject where keys are invoice IDs and values are amounts in cents. Distributes payment across multiple invoices. Example: { "456": 3000, "789": 2000 }
Behavior2/5

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

No behavioral details are provided beyond the minimal 'Record a payment'. There is no mention of side effects, required permissions, idempotency, or error handling. With no annotations, the description carries the full burden but fails to disclose key behaviors.

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?

The description is very short (two sentences) and concise. However, the second sentence introduces confusion by referencing an external tool that conflicts with the schema, reducing the effectiveness of the conciseness.

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?

For a tool with 12 parameters, a nested object, and no output schema, the description is severely incomplete. It does not explain the return value, validation constraints, or the relationship between the fields, leaving the agent with insufficient context.

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 covers all 12 parameters with descriptions, achieving 100% coverage. The description does not add any additional meaning beyond what the schema provides, so it meets the baseline but does not improve it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Record a payment', which is a clear verb+resource. However, it then says 'Use apply_payments to distribute a payment across multiple invoices', which contradicts the input schema that includes an 'apply_payments' parameter for distribution. This creates confusion about the tool's actual scope.

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?

The description only mentions one alternative (apply_payments) but does not clarify when to use this tool versus other payment-related siblings like payments_list or payments_get. No guidance on prerequisites or typical use cases.

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/advenimus/syncromsp-mcp'

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