BugSecure MCP

Get an organization’s report statistics

get_org_report_stats

Read-onlyIdempotent

Retrieve monthly report counts, severity mix, payouts, and payment standing for an organization with AI triage enabled. Requires an administrator seat.

Instructions

Report statistics for an organisation the signed-in user belongs to (it must have enabled AI triage access): monthly report counts by status, the claimed-severity mix, monthly payouts, and its payment standing (certificates issued, settled and overdue). Organisation ids: list_my_organizations. Needs an Administrator seat in that organisation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`months`	No	How many months of trends and payouts (1–24).
`organizationId`	Yes	Organization id (from list_my_organizations).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`trends`	No
`payouts`	No
`standing`	No
`severityDistribution`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.0Sep 26, 2026

changedOutput schema / properties / standing / properties / totalIssued / description

Previous value: -"Payout certificates issued."New value: +"Payout certificates issued (null when not shown)."

changedOutput schema / properties / standing / properties / totalIssued / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```

changedOutput schema / properties / standing / properties / totalSettled / description

Previous value: -"Certificates the researcher confirmed as paid."New value: +"Certificates the researcher confirmed as paid (null when not shown)."

changedOutput schema / properties / standing / properties / totalSettled / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```

First observedv0.1.0Sep 25, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable context by disclosing the permission requirement (Administrator seat) and the prerequisite (AI triage access), which are not in annotations. It also clarifies the data scope (monthly trends, payouts, payment standing), providing meaningful behavioral transparency beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loads the primary action. The first sentence is dense but informative, listing the statistic types; the second covers the ID source and permission requirement. There's no fluff, though the first sentence could be slightly restructured for readability. Overall, it's efficient and well-ordered.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers prerequisites, permissions, and the nature of the data returned. Since an output schema exists, return values don't need description. The months parameter's range and the organization ID source are both addressed. The description is complete for an agent to understand when and how to call the tool without missing critical information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% – both months and organizationId have descriptions in the schema. The description reinforces that organizationId comes from list_my_organizations, a small additional hint. Since the schema already documents parameter meaning, the description adds little new semantic value, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action (report statistics for an organization) and enumerates the exact metrics returned: monthly report counts by status, claimed-severity mix, monthly payouts, and payment standing. It clearly distinguishes itself from sibling tools like get_org_report or list_org_reports by focusing on aggregated statistics rather than individual reports or listings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description specifies that it applies to organizations the signed-in user belongs to and that the organization must have AI triage access enabled. It also explicitly notes the Administrator seat requirement, which is critical for authorization. While it doesn't name alternative tools, it points to list_my_organizations for ID retrieval, giving clear context for when to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.