Skip to main content
Glama
Sign In
mcploy

mcploy

by ogarciabrena
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create category

loyverse_create_category

Create a new product category in Loyverse by submitting category fields via POST. If a 400 error occurs, adjust the fields and retry.

Instructions

Create a new category in Loyverse (POST /categories). Field names follow the Loyverse API v1.0 (developer.loyverse.com/docs). If a call fails with a 400, the error message from Loyverse is returned verbatim — adjust the fields and retry.

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

Input Schema

NameRequiredDescriptionDefault
bodyYesThe category fields, per the Loyverse API schema.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses error handling for 400 responses, which is helpful, but lacks details on side effects, permissions, idempotency, or return behavior.

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

Conciseness4/5

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

Two short sentences, no fluff, the purpose is front-loaded. Slightly better than average conciseness, but could be more structured (e.g., separate error info).

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?

Missing return value description (no output schema), no explanation of what the created category contains, and no mention of relationships or prerequisites. Incomplete for a creation tool with a nested body parameter.

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?

Schema coverage is 100% but the description adds little beyond stating that fields follow the API. It does not list specific fields, constraints, or examples, so it meets the baseline for high coverage without added value.

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 the action ('Create'), the resource ('category'), and the API method ('POST /categories'), which matches the tool name and distinguishes it from siblings like create_customer or create_item.

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?

No explicit guidance on when to use this tool versus alternatives. It does not mention when creation is appropriate, prerequisites, or contrast with update/delete tools.

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

Deploy Server

Other Tools