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

Check an appointment request

appointment_status

Read-onlyIdempotent

Resume an appointment request: read provider-confirmed state, preferred windows and history.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	The request or offer id from your receipt or customer link
`token`	Yes	Private token from your receipt or customer link; keep it for later visits

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that the response reflects provider-confirmed state plus preferred windows and history, which is genuinely new, but says nothing about what happens with stale/expired tokens or state values an agent might encounter.

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?

One sentence, front-loaded with the verb and resource, with no filler. The word "Resume" is slightly ambiguous for a read operation, but the rest is tight and informative.

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

Completeness3/5

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

With no output schema, the description does list the categories returned (state, windows, history), which is the main thing an agent needs. It still leaves the shape of "provider-confirmed state" undefined and gives no guidance on token expiry or failure modes for a token-authenticated read.

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% and both parameters carry descriptions (id and token origins, token reuse), so the schema carries the burden. The description adds no format, precedence, or error semantics beyond that, which is the baseline-3 case.

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 action on a specific resource (read an appointment request's provider-confirmed state, preferred windows and history), so an agent knows what comes back. It stops short of distinguishing this from the sibling request_status, which sounds like it covers similar ground.

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?

"Resume" implies continuing an in-progress request with the id and token from a prior receipt, which is implied usage guidance. There is no explicit when-to-use/when-not statement and no mention of request_status or request_appointment as alternatives, leaving the agent to infer routing.

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?