Simpler.Asia

invoice_client_create

Create a invoice_client.

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": {
      "name": "<name>"
    },
    "name": "invoice_client_create"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`email`	No
`notes`	No
`phone`	No
`address`	No
`company`	No
`contact_id`	No
`message_language`	No
`reminder_cadence`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

D1.6/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so safety profile is covered. However, the description adds nothing beyond that: it does not say whether duplicate names/emails are rejected, what happens to the non-idempotent retry case, or what the response contains. Against the lower bar set by annotations this is still a minimal contribution.

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

Conciseness2/5

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

It is a single short sentence with no waste, but that brevity reflects under-specification rather than conciseness. Nothing is front-loaded because there is nothing to front-load.

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

Completeness1/5

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

For a mutation tool with 9 parameters, 0% schema coverage, and no output schema, the definition provides no information an agent needs to call it correctly: no field meanings, no duplicate-handling behavior, no return shape, no relationship to invoice_client_upsert or contact_id.

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

Parameters1/5

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

Schema description coverage is 0% across 9 parameters, and the description names none of them. The two enums (message_language: en/ms/zh and reminder_cadence: standard/from_due/overdue_only/off) and the contact_id linkage to contact_create are completely unexplained, leaving the agent to guess at semantics.

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

Purpose2/5

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

The description restates the tool name ("Create a invoice_client") without adding any scope, and it lacks sibling differentiation in a namespace containing invoice_client_create, invoice_client_upsert, invoice_client_update, myinvois_customer_create, and contact_create. It is a tautology of the name rather than an explanation of the resource.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. The most obvious conflict, invoice_client_upsert (which creates if absent), and invoice_client_link_tenant go entirely unmentioned, and no prerequisites or preconditions are stated.

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

All Simpler.Asia 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?