Skip to content

Commit 539dd4c

Browse files
committed
Adjusting prompts and tool descriptions
1 parent f9c1bb8 commit 539dd4c

File tree

6 files changed

+73
-69
lines changed

6 files changed

+73
-69
lines changed

src/mcp/README.md

Lines changed: 47 additions & 52 deletions
Large diffs are not rendered by default.

src/mcp/prompts/crashlytics/connect.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ export const connect = prompt(
66
{
77
name: "connect",
88
omitPrefix: false,
9-
description: "Access a Firebase application's Crashlytics data.",
9+
description: "Use this command to access a Firebase application's Crashlytics data.",
1010
annotations: {
1111
title: "Access Crashlytics data",
1212
},

src/mcp/resources/guides/crashlytics_connect.ts

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ import { resource } from "../../resource";
33
export const RESOURCE_CONTENT = `
44
### Instructions for Working with Firebase Crashlytics Tools
55
6-
Only ask the user one question at a time. Do not proceed without user instructions. Upon receiving user instructions, refer to the relevant resources for guidance.
6+
When working interactively with a user, only ask the one question at a time. Do not proceed without user instructions. Upon receiving user instructions, refer to the relevant resources for guidance.
77
88
Use the \`firebase_read_resources\` tool to access the following guides.
99
@@ -16,22 +16,26 @@ Use the \`firebase_read_resources\` tool to access the following guides.
1616
3. [Firebase Crashlytics Issues Guide](firebase://guides/crashlytics/issues)
1717
This guide details how to work with issues within Crashlytics. The agent should read this guide before prioritizing issues or presenting issue data to the user.
1818
19-
4. [Investigating Crashlytics Issues](firebase://guides/crashlytics/investigations)
19+
4. [Investigating Crashlytics Issues Guide](firebase://guides/crashlytics/investigations)
2020
This guide provides instructions on investigating the root causes of crashes and exceptions reported in Crashlytics issues.
2121
22-
### Check That You Are Connected
22+
### How to Check That You Are Connected
2323
2424
Verify that you can read the app's Crashlytics data by getting the topVersions report. This report will tell you which app versions have the most events.
25-
a. Use the firebase://guides/app_id if you need to find the app_id.
25+
a. Read the firebase://guides/app_id if you need to find the app_id.
2626
b. Call the \`crashlytics_get_report\` tool to read the \`topVersions\` report.
27-
c. If you haven't read the reports guide, then the tool will include it in the response. This is OK. Simply call the tool again.
28-
d. Help the user resolve any issues that arise when trying to connect.
27+
c. Help the user resolve any issues that arise when trying to connect.
2928
30-
After confirming you can access Crashlytics, ask the user what they would like help with. Your capabilities include:
29+
After confirming that you can access Crashlytics, ask the user what they would like help with. Your capabilities include:
3130
32-
- Reading Crashlytics reports to prioritize or find important issues. Before fetching issues or reports, you MUST read both the firebase://guides/crashlytics/reports and firebase://guides/crashlytics/issues guides to know how to best help users with this.
33-
- Investigating bug reports using Crashlytics event data. Before attempting to investigate an individual issue, you MUST read the firebase://guides/crashlytics/investigations guide to know how to best help users with this.
34-
- Proposing code changes to resolve identified bugs.
31+
- *Reading Crashlytics reports to prioritize or find important issues.*
32+
Before fetching reports, read the critical instructions for the \`crashlytics_get_report\` tool in the [Firebase Crashlytics Reports Guide](firebase://guides/crashlytics/reports).
33+
34+
- *Investigating bug reports using Crashlytics event data.*
35+
Before attempting to investigate an individual issue, read the [Investigating Crashlytics Issues Guide](firebase://guides/crashlytics/investigations) to understand the best practices for debugging issues.
36+
37+
- *Proposing code changes to resolve identified bugs.*
38+
3539
`.trim();
3640

3741
export const crashlytics_connect = resource(

src/mcp/resources/guides/crashlytics_issues.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ const RESOURCE_CONTENT = `
55
66
When displaying a list of issues, use the following format:
77
8-
1. Issue <issue id>
8+
1. Issue <full issue id>
99
* <the issue title>
1010
* <the issue subtitle>
1111
* **Description:** <a discription of the issue based on information from the tool response>

src/mcp/resources/guides/crashlytics_reports.ts

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,15 @@ When setting report filters adhere to the following instructions.
8888
* Report responses grouped by issue will include a sample event URI. Use the "crashlytics_batch_get_events" tool to fetch the complete record for any sample event.
8989
9090
* When investigating an issue, use the appropriate top devices and top operating systems reports to understand what systems are impacted by the problem. Pass the "issueId" in the filter to narrow any report to a specific issue.
91+
92+
### How to Display Issues
93+
94+
When displaying a list of issues, use the following format:
95+
96+
1. Issue <full issue id>
97+
* <the issue title>
98+
* <the issue subtitle>
99+
* **Description:** <a discription of the issue based on information from the tool response>
91100
`.trim();
92101

93102
export const crashlytics_reports = resource(

src/mcp/tools/crashlytics/reports.ts

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -40,11 +40,7 @@ export const get_report = tool(
4040
{
4141
name: "get_report",
4242
description:
43-
`**REQUIRED PREREQUISITE:** READ firebase://guides/app_id, firebase://guides/crashlytics/reports, and firebase://guides/crashlytics/issues.
44-
**DO NOT FETCH DATA FIRST. IT WILL CAUSE ERRORS AND WASTE TOKENS AND TIME. READING THE GUIDES IS THE MOST EFFICIENT WAY TO GET THE ANSWERS YOU WANT.**
45-
AGENTS MUST READ these guides to fetch, format, and interpret report results or TOOL CALLS WILL FAIL.
46-
47-
Use this to request numerical reports from Crashlytics.
43+
`Use this to request numerical reports from Crashlytics. The result aggregates the sum of events and impacted users, grouped by a dimension appropriate for that report. Agents must read the [Firebase Crashlytics Reports Guide](firebase://guides/crashlytics/reports) using the \`firebase_read_resources\` tool before calling to understand criticial prerequisites for requesting reports and how to interpret the results.
4844
`.trim(),
4945
inputSchema: ReportInputSchema,
5046
annotations: {

0 commit comments

Comments
 (0)