Skip to main content
Glama
advenimus

SyncroMSP MCP Server

admin_create_purchase_order

Create a purchase order for a vendor with required vendor ID and optional details such as dates, notes, and costs.

Instructions

Create a purchase order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vendor_idYesVendor ID (required)
user_idNoUser ID
location_idNoLocation ID
expected_dateNoExpected delivery date
due_dateNoDue date
order_dateNoOrder date
paid_dateNoPaid date
general_notesNoNotes
shipping_notesNoShipping notes
shipping_centsNoShipping cost in cents
other_centsNoOther costs in cents
discount_percentNoDiscount %
delivery_trackingNoTracking number
Behavior2/5

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

With no annotations, the description carries full burden but only states the obvious. It does not disclose side effects, validation, or success/failure behavior.

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 one-sentence description is appropriately concise, but it adds minimal value. It is not verbose, but also not highly informative.

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?

With 13 parameters and no output schema, the description lacks completeness. It does not explain return values, error handling, or typical usage patterns.

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%, so baseline is 3. The description adds no extra meaning beyond the schema, hence adequate but not improved.

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

Purpose4/5

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

The description 'Create a purchase order' clearly identifies the action (create) and resource (purchase order). It is specific but does not differentiate from sibling tools beyond the name.

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 guidance on when to use this tool vs alternatives. No context on prerequisites, constraints, or typical scenarios is provided.

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