Skip to content

Commit 300d0e6

Browse files
committed
feat(prompts): update allocations
1 parent 25acbc1 commit 300d0e6

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

src/tools/allocations.ts

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,8 +79,8 @@ export interface AllocationsResponse {
7979
// Tool metadata
8080
export const listAllocationsTool = {
8181
name: "list_allocations",
82-
description:
83-
"List allocations that your account has access to from the DoiT API",
82+
description: `List allocations for the report or run_query configuration that your account has access to from the DoiT API.
83+
Allocations in the DoiT Cloud Intelligence Platform are a powerful feature that allows you to group and attribute cloud costs to specific business units, teams, projects, or any other logical grouping relevant to your organization.`,
8484
inputSchema: {
8585
type: "object",
8686
properties: {

src/utils/prompts.ts

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ export const prompts = [
1717
{
1818
name: "Query Best Practice",
1919
description: "Best practice reminder for running queries",
20-
text: `Before running a query, always check the filter fields explanation and dimensions.`,
20+
text: `Before running a query, always check the filter fields explanation dimensions and allocations.`,
2121
},
2222
{
2323
name: "Document Output Reminder",
@@ -27,7 +27,7 @@ export const prompts = [
2727
{
2828
name: "Generate Report Command",
2929
description: "Template for generating cost reports",
30-
text: `To create a cost report, first check if you need specific dimensions with:\nlist_dimensions(filter: "type:fixed")\n\nThen check if there is similar reports with list_reports and get_report_results. when you understand the structure Then run a query like:\nrun_query({\n config: {\n dataSource: "billing",\n metric: { type: "basic", value: "cost" },\n timeRange: { mode: "last", amount: 1, unit: "month", includeCurrent: true },\n group: [{ id: "service_description", type: "fixed", limit: { metric: { type: "basic", value: "cost" }, sort: "desc", value: 10 } }]\n }\n})`,
30+
text: `To create a cost report, first check if you need specific dimensions with:\nlist_dimensions(filter: "type:fixed") and allocations with list_allocations(filter: "type:fixed")\n\nThen check if there is similar reports with list_reports and get_report_results. when you understand the structure Then run a query like:\nrun_query({\n config: {\n dataSource: "billing",\n metric: { type: "basic", value: "cost" },\n timeRange: { mode: "last", amount: 1, unit: "month", includeCurrent: true },\n group: [{ id: "service_description", type: "fixed", limit: { metric: { type: "basic", value: "cost" }, sort: "desc", value: 10 } }]\n }\n})`,
3131
},
3232
{
3333
name: "Generate Anomalies Document",
@@ -50,8 +50,8 @@ export const prompts = [
5050
text: `Create a document (Artifacts) with a table to display invoice details. Include the following columns: Invoice ID, Invoice Date, Due Date, Status, Total Amount, Balance Amount, Currency, and URL. For line items, create a separate table with columns: Description, Details, Price, Quantity, Type, and Currency. Add any relevant payment status or due date alerts. (Do not generate code, only a document)`,
5151
},
5252
{
53-
name: "DoiT MCP Server tools output",
54-
description: "Guidance for tool output formatting",
55-
text: `Tools results should use the Document artifact type if possible. You must never use the code artifact type or to analyze the results of a tool with code/javascript.`,
53+
name: "Allocations Usage Guidance",
54+
description: "Guidance for using allocations effectively",
55+
text: `Use the list_allocations tool to explore available allocations. Select allocations that best match your reporting needs, and always review the filter fields reference for optimal filtering.`,
5656
},
5757
];

0 commit comments

Comments
 (0)