ChatGPT Plugin

DSTI School of Engineering

Apply to DSTI programmes

Brand: DSTI School of Engineering

Category: Pending
Primary Subcategory: Pending

Integration details

Description

Apply to DSTI School of Engineering with guided support in ChatGPT. Explore programmes and entry requirements, start or resume an application, review what remains, prepare updates, and submit only after your explicit confirmation. Approved study-abroad agencies can also support applicants they represent. Guidance comes directly from DSTI's application system. Documents, identity checks, payments and restricted personal information remain within the secure DSTI Application Portal.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: DSTI School of Engineering
Access: Account required
First tracked: 2026-10-15
Tool count: 23
Geography: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce DSTI School of Engineering has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

23 tools agents can invoke

Use after explicit Agent approval to submit the latest exact DSTI-held preview.
agent.confirm_submit_application
Use after explicit approval to submit the latest exact DSTI-held preview.
applicant.confirm_submit_application
Use after explicit Agent approval of the latest exact update preview. Then get a fresh draft before claiming success.
agent.confirm_update_application
Use after explicit approval of the latest exact update preview. Then get a fresh draft before claiming success.
applicant.confirm_update_application
Represented saved conversation: must use for 'Do I need?', 'Do I owe?', why or accepted evidence. Backend only; never infer. Supporting documents and 'which supporting document' use this tool, not agent.preview_submit_application. Reauthorise mailbox; do not precede with agent.get_identity_context. Call once for every explicitly requested requirement topic; give one final answer. If unresolved, ask missing_inputs; make no further tool call until the user answers. Never silently end after a tool result. Satisfied means required and complete; never report it as not required or not applicable. State waived, already paid, not-applicable or deferred. Never replace a decision with a hand-off; use agent.get_secure_web_handoffs only for where/how. If guidance says secure Web or Contact DSTI Admissions, relay it. Do not ask for removed missing inputs.
agent.explain_application_requirement
USE: Backend tool: current or saved requirement questions: "Do I need?" "Do I owe?", reasons, accepted evidence, direct Year 2 and supporting documents. READINESS: Use applicant.preview_submit_application only for whole-application readiness. CALL: Call once per topic. Ask missing_inputs. Stop for the answer. Return a final answer. COMBINED: For English evidence and fees, call once per topic. Report both saved decisions. For mixed prospective and saved requirements, report both. STATUS: Satisfied requirement means required and complete. Waived, paid, not applicable, deferred. Preserve backend decision in Web hand-offs. Relay secure Web or Contact DSTI Admissions guidance. Do not ask removed missing inputs.
applicant.explain_application_requirement
Use for a represented applicant's prospective 'Can I', 'Do I need', 'Do I owe an application fee?', why or evidence question before a saved application exists. Never use for 'my represented applicant'; call agent.get_my_applications. Ask missing_inputs one at a time; never infer facts. Backend decides. For French language and Alternance, always call with all supplied facts even if citizenship is absent; do not claim unavailable. Programme, study route, intake and study rhythm use one call with public values. Alternance uses Study route and delivery, not Programme entry. Programme-and-route direct Year 2 or second-year entry examination availability uses applicant.get_application_entry_options. Personal academic eligibility uses this tool with facts.direct_entry_year2 true; not for only programme and route. Do not discover; never retry an internal code; always return a final answer.
agent.explain_prospective_requirement
USE: Backend tool before an application exists. Needs no application ID. "I want to apply" is prospective. Topics: personal eligibility, fees, French evidence, Alternance and study rhythm. CURRENT: "My application" means an existing application. Current context wins. Current or saved applications use applicant.explain_application_requirement. Do not search. ENTRY: applicant.get_application_entry_options for intake timing, route-only Year 2 exam availability. For personal Year 2 eligibility use facts.direct_entry_year2=true. INPUT: Send all supplied programme, study route, intake, application route, citizenship, language and study-rhythm facts once. For French evidence call even without citizenship. Ask missing_inputs. Never infer. Treat absent citizenship as missing input. ALTERNANCE: Alternance is an application route. Programme entry is separate. Study route is delivery or location. OUTPUT: After an internal-code rejection, return a final answer. Do not retry. MIXED: Call both requirement tools. Report both results.
applicant.explain_prospective_requirement
Editing only; contains no requirement decision. Do not use for whether, why or evidence; use agent.explain_application_requirement.
agent.get_application_draft
Editing only; contains no requirement decision. Do not use for whether, why or evidence; use applicant.explain_application_requirement.
applicant.get_application_draft
Sole tool for one programme and route to list intakes, decide whether an intake choice is required, including Online timing, or report direct Year 2 and second-year entry examination availability. Use for "Can I apply directly to Year 2" with only programme and study route. Never use for a possessive current or saved application: discover that application and use applicant.explain_application_requirement. Never use after applicant.get_my_applications. For an exact start-page request, do not call this tool; call prepare_application_start directly unless the user asks to check timing first. Present backend timing; never expose internal codes.
applicant.get_application_entry_options
Use when resolving the verified mailbox to one active DSTI-approved agency. Present both the returned agency name and canonical Agent code.
agent.get_identity_context
Must call for 'my represented applicant', an applicant 'I am managing', or to list represented applications when there is no application ID. Do not ask for an ID first. It reauthorises the mailbox; do not precede it with agent.get_identity_context. After results, do not call this discovery tool again in the same request. Use it when there is no ID, including a fee or supporting-document question. If empty, say that no authorised represented application is available; never infer or disclose whether another application exists or who represents it. Do not repeat the Agent's claim about another agency as fact. Refer to DSTI support for representation changes.
agent.get_my_applications
FIRST ROUTING RULE: whenever "my" modifies "application", including "my Online Asynchronous application", this discovery call is required first unless the user explicitly plans or starts a new one. Must call for the applicant's current application, saved application or existing application with no application ID, including a fee, language, evidence, entry or study-route question. Do not ask the applicant for its programme or study route; read them from the returned application. Then use applicant.explain_application_requirement for a requirement. Use returned identifiers; do not call this discovery tool again in the same request. For a home address, the next call is applicant.get_secure_web_handoffs. Never ask for or accept a home address in ChatGPT. Do not use when the user asks to start a different application. Its links must never be described as starting another application; only applicant.prepare_application_start prepares that hand-off. "I want to apply" is prospective intent: do not discover. Do not use for a prospective question; use applicant.explain_prospective_requirement.
applicant.get_my_applications
A home address is precise location data. For any represented home-address view or change, call this secure Web hand-off. Never ask for or accept a home address in ChatGPT; do not ask the user to paste protected values. Also use it for protected personal, contact, precise location or guardian data, documents, identity verification or a fee action. Recheck the agency relationship. Return exact Web purposes. Do not claim unsupported editability. Never use for 'Do I owe an application fee?', waived or already paid. For a fee decision, use agent.explain_application_requirement.
agent.get_secure_web_handoffs
A home address is precise location data. For any home-address view or change, call this secure Web hand-off. Never ask for or accept a home address in ChatGPT; do not ask the user to paste protected values. Also use it for protected personal, contact, precise location or guardian data, documents, identity verification or a fee action. Return ownership-checked Web routes and exact purposes. Do not claim unsupported editability. Never use for 'Do I owe an application fee?', waived or already paid. For a fee decision, use applicant.explain_application_requirement.
applicant.get_secure_web_handoffs
List all programmes, study routes and current intakes. Broad landscape only; never use for one programme and route: use applicant.get_application_entry_options. One backend call, no fan-out; public labels only.
applicant.list_programmes_routes_and_intakes
Open the Agent Web start page. Call this tool directly for an exact programme and route plus an intake, timing is determined automatically, or no selectable intake. Pass cohort null in the latter two cases. Cohort null does not mean timing is automatic; automatic false means published course schedule. Do not use applicant tools. Represented applicant is already an explicit Agent-routing cue; do not ask the user to reconfirm agency status. Send only programme, route and intake; copy exact public labels. Protected applicant and guardian data stay outside ChatGPT.
agent.prepare_application_start
Call this tool directly. Copy the exact public labels for an intake, timing is determined automatically, or no selectable intake. Pass cohort null; cohort null does not mean timing is automatic: automatic false means published course schedule. This pre-creation hand-off requires no existing application or application identifier and does not create, update or submit an application. Call it for an exact new start even when the applicant already has another application. When the user asks to check timing first, call entry options and then call this tool with the returned public timing decision. Published-course timing with no selectable intake is supported before any application exists. Protected.
applicant.prepare_application_start
confirmation_summary: explicitly ask; do not submit. 'which supporting document': agent.explain_application_requirement. If Agent discovery returns more than one authorised application and the user has not identified one, do not choose by status and do not call this tool. Ask the Agent to choose using only privacy-minimised authorised summaries before preparing a preview.
agent.preview_submit_application
Submission readiness or every blocker: use this whole-application validator. Never use for 'which supporting document'; use applicant.explain_application_requirement.
applicant.preview_submit_application
Use only after the user asks to save or change fields. Reauthorise, validate and preview without application mutation.
agent.preview_update_application
Use only after the user asks to save or change fields. Validate and preview without application mutation.
applicant.preview_update_application

FAQs