Skip to main content
Glama

Find inspection times

find_inspection_times

Finds real inspection or panel-cleaning appointment times at a street address, for a person with no Otovo account or scheduling link. The times come from the dispatch planner, so a crew can reach the address in each one. Creates the person's customer record (name, contact details, address) so the planner can route to it; books nothing. Each returned slot is a selected_slot value for a request_inspection change. Serves every Otovo region: without a connected account the scheduling code, preview or address selects the region; a connected customer is served where their account lives.

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": {
      "contact": "<contact>",
      "address": "<address>"
    },
    "name": "find_inspection_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoAnything the crew should know before arriving.
addressYes
contactYes
promo_codeNoA promo code the customer gave. The answer's charge is the price with it and promo says whether it applied or why it was refused; pass it again in request_inspection.
service_typeNoWhich visit to plan. Defaults to inspection.
preferred_week_startNoEarliest date to search from, YYYY-MM-DD. Omit for the soonest available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / promo_code
      Added value: +{
      +  "description": "A promo code the customer gave. The answer's charge is the price with it and promo says whether it applied or why it was refused; pass it again in request_inspection.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description supplies the substance: a customer record is created as a side effect, nothing is booked, times are sourced from the dispatch planner and are crew-reachable, and region resolution differs for connected vs. unconnected customers. That is exactly the behavioral context annotations cannot convey.

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?

Front-loaded with purpose and the key non-booking constraint, and every sentence carries information. The region-resolution sentence is dense and slightly tangential to invocation, but not wasteful.

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?

With no output schema, the description does the necessary work of explaining what comes back (slots usable as selected_slot, plus charge/promo) and warns that a customer record is created. For a 6-parameter nested-schema tool it is close to complete, missing only duplicate-call/idempotency behavior.

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 67% with solid per-field descriptions, so the schema does most of the work. The description adds output-side meaning (returned slots map to selected_slot, promo_code is echoed in request_inspection and the answer's charge/promo fields) but says nothing extra about service_type, preferred_week_start, notes, or the nested address/contact objects.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (finds real inspection or panel-cleaning appointment times at a street address) and scopes the audience (a person with no Otovo account or scheduling link). The added 'books nothing' clause separates it from any booking/confirmation sibling, so an agent can place it without opening a schema.

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

Usage Guidelines4/5

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

Gives a clear when-to-use condition (no account or scheduling link) and a downstream when (each slot is a selected_slot for a request_inspection change). It does not explicitly name an alternative for the booked/account-holding case, leaving that routing to inference.

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.