execute_graphql
ChatGPTUse this when no other specific tool covers the data needed. Executes a custom GraphQL query against the Field Control API. Requires a valid GraphQL query string. Do not use when a specific search or get tool is available for the entity.
get_customer_details
ChatGPTUse this when the user asks about a specific customer by ID. Returns complete customer data including name, document number, all contacts, address, tags, statistics and attachments. Do not use for listing multiple customers — use search_customers instead.
get_employee_details
ChatGPTUse this when the user asks about a specific employee or technician by ID. Returns complete employee data including name, email, address, contract details, work schedule, groups, skills and device info. Do not use for listing multiple employees — use search_employees instead.
get_equipment_details
ChatGPTUse this when the user asks about a specific equipment by ID. Returns complete equipment data including name, serial number, model, manufacturer, customer, location and maintenance history. Do not use for listing multiple equipments — use search_equipments instead.
get_location_details
ChatGPTUse this when the user asks about a specific service location by ID. Returns complete location data including name, address, customer, contacts, attachments, territories and responsible person. Do not use for listing multiple locations — use search_locations instead.
get_order_details
ChatGPTUse this when the user asks about a specific work order by ID or needs detailed information about one order. Returns complete order data including tasks, equipments, customer, employee, services, deadline, address and comments. Do not use for listing multiple orders — use search_orders instead.
get_part_details
ChatGPTUse this when the user asks about a specific inventory part by ID. Returns complete part data including name, code, description, quantity in stock and unit price. Do not use for listing multiple parts — use search_parts instead.
get_part_unit_details
ChatGPTUse this when the user asks about a specific serialized part unit by ID. Returns complete unit data including serial number, status, location history and associated order. Do not use for listing multiple units — use search_part_units instead.
get_product_details
ChatGPTUse this when the user asks about a specific product by ID. Returns complete product data including name, code, description, price and stock info. Do not use for listing multiple products — use search_products instead.
get_quotation_details
ChatGPTUse this when the user asks about a specific quotation or estimate by ID. Returns complete quotation data including items, prices, customer, discounts and approval status. Do not use for listing multiple quotations — use search_quotations instead.
get_service_details
ChatGPTUse this when the user asks about a specific service type by ID. Returns complete service data including name, description, pricing and configuration. Do not use for listing multiple services — use search_services instead.
get_storage_details
ChatGPTUse this when the user asks about a specific storage location or warehouse by ID. Returns complete storage data including name, address and inventory summary. Do not use for listing multiple storages — use search_storages instead.
get_task_details
ChatGPTUse this when the user asks about a specific task by ID. Returns complete task data including description, status, scheduled date, duration, assigned employee, order reference and checklist items. Do not use for listing multiple tasks — use search_tasks instead.
get_ticket_details
ChatGPTUse this when the user asks about a specific support ticket by ID. Returns complete ticket data including subject, description, status, priority, requester, assigned employee and conversation history. Do not use for listing multiple tickets — use search_tickets instead.
get_user_details
ChatGPTUse this when the user asks about a specific system user by ID. Returns complete user data including name, email, role, phone and profile settings. Do not use for listing multiple users — use search_users instead.
introspect_schema
ChatGPTUse this when you need to discover available types, fields and operations in the data model. Introspects the GraphQL schema structure.
search_customers
ChatGPTUse this when the user wants to find, list or search customers (clientes). Returns paginated results with customer name, document number, contact info and address. Supports filtering by name, city, state, document number, tags and rating. Do not use for getting details of a single customer — use get_customer_details instead.
search_employees
ChatGPTUse this when the user wants to list, search or filter field technicians/employees (técnicos/funcionários). Returns paginated results with employee name, email, groups and contract status. Supports filtering by name, active status, group and territory. Do not use for getting details of a single employee — use get_employee_details instead.
search_equipments
ChatGPTUse this when the user wants to find, list or search equipments (equipamentos). Returns paginated results with equipment name, serial number, model, customer and location. Supports filtering by name, serial number, customer and location. Do not use for getting details of a single equipment — use get_equipment_details instead.
search_locations
ChatGPTUse this when the user wants to find, list or search service locations (locais de atendimento). Returns paginated results with location name, address, customer and contact info. Supports filtering by name, city, state, customer and territory. Do not use for getting details of a single location — use get_location_details instead.
search_order_equipments
ChatGPTUse this when the user wants to see which equipments were serviced in work orders. Returns paginated results with equipment name, order reference and service details.
search_order_parts_used
ChatGPTUse this when the user wants to see which parts were consumed in field service orders. Returns paginated results with part name, quantity, order reference and technician.
search_orders
ChatGPTUse this when the user wants to list, search or filter work orders (ordens de serviço). Returns paginated results with order ID, identifier, status, customer name, scheduled date and assigned employee. Supports filtering by date range, status, customer, employee and territory. Do not use for getting details of a single order — use get_order_details instead.
search_part_types
ChatGPTUse this when the user wants to see part categories or types. Returns list of part types with name and description.
search_part_units
ChatGPTUse this when the user wants to list individual serialized part units. Returns paginated results with unit serial number, status and location. Supports filtering by part and status. Do not use for getting details of a single unit — use get_part_unit_details instead.
search_parts
ChatGPTUse this when the user wants to find or list inventory parts (peças). Returns paginated results with part name, code, quantity and unit price. Supports filtering by name and code. Do not use for getting details of a single part — use get_part_details instead.
search_product_types
ChatGPTUse this when the user wants to see product categories or types. Returns list of product types with name and description.
search_products
ChatGPTUse this when the user wants to find or list products (produtos). Returns paginated results with product name, code and price. Supports filtering by name and type. Do not use for getting details of a single product — use get_product_details instead.
search_quotations
ChatGPTUse this when the user wants to list, search or filter quotations/estimates (orçamentos). Returns paginated results with quotation number, customer, total value, status and date. Supports filtering by status, customer and date range. Do not use for getting details of a single quotation — use get_quotation_details instead.
search_schema
ChatGPTUse this when looking for specific data fields or entities in the schema. Searches for types or fields matching a keyword.
search_services
ChatGPTUse this when the user wants to list or search service types (tipos de serviço). Returns paginated results with service name, description and pricing. Supports filtering by name. Do not use for getting details of a single service — use get_service_details instead.
search_storage_items
ChatGPTUse this when the user wants to check inventory items in a specific warehouse. Returns paginated results with item name, quantity and location within storage.
search_storage_movements
ChatGPTUse this when the user wants to track inventory movements or stock changes (movimentações de estoque). Returns paginated results with movement type, item, quantity, date and responsible person.
search_storage_parts
ChatGPTUse this when the user wants to check part stock levels in a specific storage. Returns paginated results with part name, quantity available and storage location.
search_storage_products
ChatGPTUse this when the user wants to check product stock levels in a specific storage. Returns paginated results with product name, quantity available and storage location.
search_storage_requests
ChatGPTUse this when the user wants to see pending inventory requests from field technicians (requisições de estoque). Returns paginated results with request status, items requested and requester.
search_storages
ChatGPTUse this when the user wants to list storage locations or warehouses (almoxarifados). Returns paginated results with storage name and address. Do not use for getting details of a single storage — use get_storage_details instead.
search_tasks
ChatGPTUse this when the user wants to list, search or filter tasks (atividades/tarefas). Returns paginated results with task ID, description, status, scheduled date, duration and assigned employee. Supports filtering by date range, status, employee and order. Do not use for getting details of a single task — use get_task_details instead.
search_tickets
ChatGPTUse this when the user wants to list, search or filter support tickets (chamados). Returns paginated results with ticket subject, status, priority, requester and creation date. Supports filtering by status, priority, requester and date range. Do not use for getting details of a single ticket — use get_ticket_details instead.
search_users
ChatGPTUse this when the user wants to list or search system users who have access to the account. Returns paginated results with user name, email and role. Supports filtering by name and email. Do not use for getting details of a single user — use get_user_details instead.
search_work_services
ChatGPTUse this when the user wants to list work services performed on orders (serviços executados). Returns paginated results with service name, quantity and value.
validate_query
ChatGPTUse this when you need to check if a GraphQL query is syntactically correct before executing it. Validates a query against the schema without running it.
