Skip to main content
Glama

My Otovo

get_my_otovo
Read-onlyIdempotent

Reads what a customer can see in their Otovo portal, one view at a time. Changes nothing. With a scheduling code and no account, three views: booking_status (the address, services offered, the visit already scheduled and whether it can be moved or cancelled, open access questions, the support line), booking_options (code and service_type, optional week_start, location_id and promo_code: bookable times for a new visit, best first, with the price and what the promo code does) and reschedule_options (code, optional week_start: times the scheduled visit can move to). With a connected account, site_id selects one of the customer's sites when they have several: sites, profile, home, summary; monitoring (production now, equipment status, alerts and when each reading was taken; a missing or stale reading is not zero production), monitoring_page, monitoring_history (node_id, query range day|week|month|year and date), monitoring_devices (node_id), monitoring_device (node_id, device_id), monitoring_energy_rate; connect_system (the monitoring providers Otovo connects, the fields each connection needs and the portal's setup steps; id = one provider); energy, energy_usage (query start_date, end_date, granularity), energy_bills, energy_plans; service (visits, work orders, bookable services), appointment (id), appointment_tracking (id: where the crew is on the day), scheduling (what can be booked or moved, open access questions), booking_options (service_type, optional week_start and promo_code) and reschedule_options (optional week_start); work_order (id), repair (id), site_report (id; photos stay in the portal); quotes, quote (id); billing, billing_records (query limit, cursor), billing_record (id; the invoice PDF is a portal link), payment_methods, subscription, subscription_plans, subscription_terms (query tier, billing_interval); documents (pending, signed, project and historical); leases, lease (id); hour_bank; notification_settings. Reading booking times for a connected customer can create their own Otovo scheduler link; nothing is sent to them. 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": {
      "view": "<view>"
    },
    "name": "get_my_otovo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe record a single-record view is about: an appointment, work order, site report, quote, billing record (its quote id), lease (project id), or a provider key for connect_system.
codeNoWithout an account: the customer's scheduling code, the last part of the otovo.com/book/... link they were sent. It cannot be looked up from other details.
viewYesWhat to read. See the tool description for what each view holds and which parameters it takes.
queryNoExtra filters the view takes, as named in the description: for example {"range":"month","date":"2026-10-01"} for monitoring_history, {"limit":20} for billing_records, {"tier":"care"} for subscription_terms.
node_idNoA monitoring node from view monitoring (monitoring_history, monitoring_devices, monitoring_device).
site_idNoConnected customers: one of their own sites, a site_id from view sites. Needed when they have more than one.
device_idNoA device from view monitoring_devices (monitoring_device).
promo_codeNobooking_options: a promo code the customer gave. The answer's charge is the price with it and promo says whether it applied, their Otovo Care discount is larger, or why it was refused.
week_startNobooking_options, reschedule_options: earliest date to search from, YYYY-MM-DD. Step it forward a week at a time to look further out.
location_idNobooking_options: which property, when the booking covers more than one.
service_typeNobooking_options: the kind of new visit. booking_status or view scheduling lists what is actually offered.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / promo_code
      Added value: +{
      +  "description": "booking_options: a promo code the customer gave. The answer's charge is the price with it and promo says whether it applied, their Otovo Care discount is larger, or why it was refused.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / service_type / enum
      Previous value: -[
      -  "panel_cleaning",
      -  "inspection",
      -  "inspection_panel_cleaning",
      -  "generator",
      -  "project_consultation"
      -]New value: +[
      +  "panel_cleaning",
      +  "inspection",
      +  "inspection_roof",
      +  "inspection_panel_cleaning",
      +  "inspection_roof_panel_cleaning",
      +  "generator",
      +  "project_consultation"
      +]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already carry readOnly/idempotent/non-destructive/closed-world, but the description adds non-obvious behavior: reading booking times can create the customer's own scheduler link while nothing is sent to them, photos and invoice PDFs stay as portal links, and a stale monitoring reading is not zero production. These are genuine disclosures the annotations cannot express; only rate limits and error behavior are missing. The scheduler-link side effect is not a contradiction of readOnlyHint since no customer data is modified, but it deserves the extra context it gets.

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?

Front-loaded with a clear purpose and side-effect statement, but the body is one enormous run-on paragraph enumerating every view, which is hard to scan for a 39-value enum. Given the surface area the length is defensible, but grouping views into account / monitoring / energy / service / billing blocks would substantially improve retrievability.

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

Completeness5/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 carries the return-value burden and does so for every view (what booking_status, monitoring, billing_record, connect_system etc. return), plus parameter requirements per view, region resolution, and side effects. For a router tool of this complexity that is essentially the full picture an agent needs to select a view and call it.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines each parameter, yet the description adds the crucial routing layer: which of the 11 parameters each view accepts (e.g. week_start and service_type belong to booking_options, node_id to the monitoring views, id to single-record views and connect_system). It also clarifies 'id' is a quote id for billing_record and a project id for lease, which the schema text only partly covers.

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 ("Reads what a customer can see in their Otovo portal, one view at a time. Changes nothing."), which immediately frames it as the read-only aggregator among siblings like confirm_change and preview_change. The 39-view enumeration reinforces the scope, though it never explicitly names the write-side siblings it should be paired with.

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 strong conditional guidance: without an account a scheduling code selects three views, with a connected account site_id selects a site, and region resolution is explained for both paths. It stops short of explicit "use X instead when Y" routing against the sibling tools, so an agent must infer the handoff to preview_change/confirm_change.

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.