Linklamp: Switch swap or repatch visit in Dearborn, MI, under your remote engineer

Send Linklamp a requirement

submit_request

Send Linklamp a requirement (Switch swap or repatch visit in Dearborn, MI, under your remote engineer). The request is recorded with a reference at once. Linklamp reads the scope, open questions and any words kept as written, then prices and schedules the visit and emails a proposal: visit duties, exclusions, price and a proposed time inside the client's window. Without an email address the request is still recorded, reply_by_email is listed in missing_specifications, and no proposal can be sent until an address is given in a continuation. Nothing is ordered, booked or committed until the buyer agrees terms; a time is confirmed only on the appointment status page, after a provider confirms it. Contact details are kept apart from the requirement, while we correspond or do business and for 24 months after, so a later request picks up where it left off; ask us to delete them at any time. It is answered with a receipt: keep its id and token to read its status (request_status), to add details later (continuation) and to act on an offer made in reply. A requirement is not an order and costs nothing.

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

Input Schema

Name	Required	Description
`need`	Yes	The requirement in the buyer's own words
`action`	No
`budget`	No
`timing`	No
`contact`	No
`quantity`	No
`geography`	No
`continuation`	No	The receipt id and token of an earlier request, to add to it instead of opening a new one
`specifications`	No	Fields from the request_schema describe_business returns
`requested_fields`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Beyond the annotations it discloses real side effects and constraints: the request is recorded immediately with a reference, Linklamp emails a proposal, no proposal can be sent without an email (reply_by_email lands in missing_specifications), nothing is committed until the buyer agrees, and contact data is kept 24 months with deletion on request. That is precisely the non-obvious behavior an agent needs for a create-and-dispatch tool.

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 purpose is front-loaded and the retention/no-commitment sentences earn their space, but several sentences are overloaded multi-clause runs, and the opening parenthetical about a 'Switch swap or repatch visit in Dearborn, MI' reads as an example masquerading as a definition. It could be tightened without losing any behavioral content.

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

Completeness4/5

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

For a 10-parameter, deeply nested mutation with no output schema and low schema coverage, the description covers the important gaps: what the buyer gets back (a receipt id and token, missing_specifications), the asynchronous proposal flow, and the commitment boundary. Only the enum-valued action and the structured budget/timing/quantity semantics remain unexplained.

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?

With only 30% schema description coverage across 10 nested parameters, the description must carry meaning, and it adds some: 'words kept as written' maps to need, the missing-email behavior maps to contact.email, and continuation is explained as an earlier receipt id and token. It says nothing about action, budget, timing, quantity, geography, specifications or requested_fields, leaving most nested fields undocumented in both places.

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 names a specific verb and resource ('Send Linklamp a requirement') and is explicit that this captures scoped work to be priced and scheduled, not an order. However, it never distinguishes itself from the near-identical sibling send_requirement or submit_purchase_order, leaving the agent to guess which submission tool applies.

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

Usage Guidelines3/5

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

It routes the agent for later steps ('read its status (request_status)', 'add details later (continuation)') and frames the tool as pre-order ('A requirement is not an order and costs nothing'), which implies submit_purchase_order is the ordering path. But there is no explicit when-not statement and no differentiation from send_requirement, so usage is inferred rather than stated.

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

All Linklamp: Switch swap or repatch visit in Dearborn, MI, under your remote engineer 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?