Bayline: truckload, LTL and intermodal freight lanes; warehouse space requirements

Change a requirement by field

edit_requirement

Idempotent

Set fields by name ({"op":"set","values":{...}}, an empty value clears) or change the list ({"op":"add"|"update"|"remove"|"replace", ...}), exactly as given: no reading. Use it to answer the open question when the answer is a value.

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": {
      "slug": "<slug>",
      "id": "<id>",
      "token": "<token>",
      "ops": "<ops>"
    },
    "name": "edit_requirement"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The requirement id from an earlier answer
`ops`	Yes
`slug`	Yes	The service, from list_propositions
`op_id`	No
`token`	Yes	Its private token (also the receipt token of the request it is sent as); keep it private
`base_revision`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare the safety profile (not read-only, idempotent, non-destructive), and the description adds meaningful behavior: ops are applied 'exactly as given: no reading' and an empty value clears a field. It does not disclose what happens on a revision conflict, whether clearing is recoverable, or how the private token is validated, which matters for a mutation tool.

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?

It is compact and every clause carries information, but the single run-on sentence front-loads JSON syntax ahead of what the tool is for. A reader gets the wire format before they know they are editing a requirement.

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 6-parameter mutation tool with four required parameters and no output schema, yet the description is silent on base_revision (presumably optimistic concurrency), op_id, and failure behavior. Given the annotation-driven safety profile it does not need to restate the write nature, but an agent still cannot tell what happens when a revision is stale or an op is rejected.

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 50% and the ops parameter is a bare array of free-form objects in the schema, so the description's explanation of op shapes (set with values, empty clears, add/update/remove/replace) genuinely compensates for the most opaque parameter. However op_id and base_revision get no explanation anywhere, and the description does not tie the ops grammar back to the required slug/id/token fields.

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 explains the op syntax for setting fields or altering a list, which implies mutation of a requirement, but it never plainly states 'modifies an existing requirement identified by slug and id'. The purpose must be reconstructed from the name, title and op grammar rather than read directly, and it is not clearly separated from siblings like answer_remedy or interpret_requirement.

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?

'Use it to answer the open question when the answer is a value' gestures at a use case but is cryptic — 'the open question' is undefined and no sibling is named as the alternative. It also never says when NOT to use it, e.g. when the answer is a document or a status change.

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

All Bayline: truckload, LTL and intermodal freight lanes; warehouse space requirements 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?