Skip to main content
Glama
Sign In
machship-mcp

machship-mcp

by devkindhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Add Permanent Pickups to Company Location

machship_add_permanent_pickups

Adds permanent scheduled pickups to a company location using a configuration payload with location ID and schedule details.

Instructions

Adds permanent scheduled pickups to a company location.

Args:

  • payload (object): Contains companyLocationId and pickup schedule details

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

Input Schema

NameRequiredDescriptionDefault
payloadYesPermanent pickup configuration including companyLocationId and schedule

Output Schema

NameRequiredDescriptionDefault
errorsNoValidation errors returned by Machship, if any
objectNoResponse payload from the Machship API

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • addedInput schema / properties / payload / propertyNames
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "errors": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Validation errors returned by Machship, if any"
+    },
+    "object": {
+      "description": "Response payload from the Machship API"
+    }
+  },
+  "type": "object"
+}
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the word "permanent," which hints at persisted recurring schedules, but it does not warn that repeated invocation on a non-idempotent endpoint may create duplicate pickup schedules, nor does it mention required auth or scope.

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, front-loaded statements with no filler; the purpose sentence comes first and the argument note follows. The 'Args:' block partially restates the schema but is justified given the payload has no declared properties.

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?

This is a non-idempotent write taking an unconstrained nested object, and the description does not describe the pickup schedule structure, what a partial or invalid payload does, or how duplicates are avoided. Presence of an output schema excuses omitting return values, but the input-side and duplicate-risk gaps remain substantial for a mutation tool.

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 payload schema is a bare object with additionalProperties {} and no defined properties, so the description's mention of companyLocationId and "pickup schedule details" is the only structural hint available and does genuinely add meaning. However, it stays vague about the schedule's actual shape (frequency, times, days), so it only marginally compensates for the vacuous schema.

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?

States a specific verb and resource: "Adds permanent scheduled pickups to a company location." The write-oriented naming plus the existence of the read-side sibling machship_get_permanent_pickups makes the distinction inferable, though the description never names that sibling explicitly.

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?

There is no when-to-use guidance, no prerequisites (e.g. the company location must already exist), and no routing to the alternatives such as machship_get_permanent_pickups to inspect existing schedules or machship_rebook_manifest_pickup. The agent is left to infer when this tool applies.

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