Skip to main content
Glama

request_visit

Send a shop on the Fifty Asks widget a visit request for your human. It is a request, not a booked appointment: status is 'requested' until the shop confirms a time ('confirmed') or declines.

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": {
      "shop_id": "<shop_id>",
      "problem": "<problem>",
      "contact_name": "<contact_name>",
      "phone": "<phone>",
      "address": "<address>",
      "preferred_times": "<preferred_times>"
    },
    "name": "request_visit"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
notesNo
phoneYesThe shop confirms by phone or text
addressYesJob address, or at least ZIP
problemYesWhat needs fixing
serviceNo
shop_idYes
agent_nameNoWhich agent you are
contact_nameYes
preferred_timesYese.g. Thursday morning

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the lifecycle: status stays 'requested' until the shop confirms ('confirmed') or declines. That is genuine value about the outcome of the call. Beyond it, there is no word on idempotency, duplicate requests, who can see the request, whether it can be withdrawn, or what the call returns, which is thin for a mutating, 10-parameter tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and resource, then the single most important semantic caveat. Nothing is wasted and no sentence is padding.

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?

Ten parameters, six required, no output schema, and no annotations mean the description has a lot of ground to cover, and it covers only the status lifecycle. An agent still does not know what comes back (a request id, shop contact details?), how the request is delivered, or how preferred_times interacts with shop confirmation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, so half the parameters (shop_id, contact_name, email, notes, service) have no documented meaning anywhere, and the description adds nothing about any of the ten. It never clarifies formats, constraints, or which fields drive confirmation routing beyond what the schema's own phone/address/preferred_times hints already say.

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: send a visit request to a shop on the Fifty Asks widget, on behalf of 'your human'. It also carves out scope versus the booking-style siblings by insisting this is a request, not a booked appointment. It stops short of naming which sibling to use for actual bookings, but the purpose is unambiguous.

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?

Usage is implied rather than stated: an agent can infer you call this when the human needs a shop visit and no time is yet agreed. There is no explicit when-not guidance and no named alternative such as book_call or book_free_check for the confirmed-slot case, leaving the agent to infer routing from the request-versus-booking distinction.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources