Cursor
Grok Bot
Grok
MuseTitle99/100
Ask Kinro about business insurance
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
Ask Kinro, a licensed business insurance broker, about the user’s business insurance: what coverage fits the business, carrier eligibility and exclusions, and quotes. Kinro’s AI advisor, Leo, answers. Kinro is not tied to any carrier: it gets real quotes from several carriers in one conversation, so the user does not have to start a separate quoting session with each carrier. Its answers rest on carrier underwriting rules and live quotes, and as the broker Kinro is accountable for its advice and carries errors and omissions insurance for it. Kinro returns coverage answers and any follow-up questions needed to prepare the request. You speak to Kinro for the user: tell it what the user needs, answer its follow-up questions from what the user has told you, ask the user what you do not know, and send the user’s follow-up requests in the same conversation. Kinro handles every conversation as a real insurance request, including on its test endpoint. When testing there and the user has you make up a business, choose details that look real, with no placeholders such as “Test Lane”, and give them as plain facts the way its owner would. Do not call the details fake, fictional, or a test, because Kinro does not quote details it is told are not real. The first call opens a Kinro insurance request for the business and saves what the user shares, so Kinro can prepare quotes. To quote, Kinro sends the business’s details to insurance carriers; carriers get no permission to contact the user. Kinro contacts the user outside this chat, by email or text, only at contact details the user shares and agrees to be contacted at. Each call sends a new message, so do not repeat a call to retry it. Kinro’s messages say what to expect next. Some answers, like quotes, arrive later: when Kinro says it is still working, call get_kinro_messages with wait set to true to get its next messages. A quote message links to the customer’s quote page on kinro.com, with the full quote and its documents: if you can open web pages, open it to go through the quote with the user, and never buy or enter payment details for them.
The description explains the capability, when to use it, and what to expect.
Inputs82/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
message
What you tell Kinro for the user: what the user wants, such as advice, a quote, or a change to one, and the facts about the business the user has given you that Kinro needs to move forward. Write it as the user’s representative; do not paste your conversation with the user, and leave out what the user said only to you, such as which tool or endpoint to use. Answer Kinro’s questions with what the user has told you, and ask the user for the rest. Never guess a fact about the business, and do not tell Kinro what to infer. Never include a Social Security number, driver’s license number, payment card number, or password.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
files › items › data
The file's contents, base64-encoded (a data: URL also works). Use this or download_url, not both.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
files › items › download_url
ChatGPT's short-lived HTTPS download link for the file. Kinro opens only links from ChatGPT's file storage; other agents send data instead.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
files › items › file_id
The chat app's ID for the file, sent with download_url.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
files › items › mime_type
The file's type, if known. Kinro checks the type from the file's contents.
Clear enough to supply this argument.
files › items › file_name
The file's name, if known.
Clear enough to supply this argument.
conversation_id
The conversation_id returned by ask_kinro. Reuse it for this conversation; omit on the first message. Never invent one or reuse another conversation's ID.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations100/100
All four behavior hints are declared.
{
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}Output schema81/100
The output schema explains the structured result.
View output schema
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"messages"
],
"properties": {
"messages": {
"type": "array",
"items": {
"type": "string"
},
"description": "Kinro's messages, oldest first, each to show the user as written, including links. When nothing new has arrived, one note says so."
},
"conversation_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The conversation_id returned by ask_kinro. Reuse it for this conversation; omit on the first message. Never invent one or reuse another conversation's ID."
}
},
"additionalProperties": false
}