contract-testing_get_team_metricsFetch metrics for all teams to review contract-testing performance and identify areas needing attention.
Fetch metrics for all teams
Toolset: Metrics
Parameters: None
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| teams | No | ||
| _links | No |
Changes observed during successful MCP inspections.
v0.43.0Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "EmbeddedLink": {
+ "additionalProperties": {},
+ "properties": {
+ "href": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "templated": {
+ "type": "boolean"
+ },
+ "title": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": {},
+ "properties": {
+ "_links": {
+ "additionalProperties": {},
+ "properties": {
+ "self": {
+ "$ref": "#/$defs/EmbeddedLink"
+ }
+ },
+ "type": "object"
+ },
+ "teams": {
+ "items": {
+ "additionalProperties": {},
+ "properties": {
+ "metrics": {
+ "additionalProperties": {},
+ "properties": {
+ "deployedVersions": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ },
+ "currentlyDeployedCount": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "environments": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "integrations": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "interactions": {
+ "additionalProperties": {},
+ "properties": {
+ "latestInteractionsCount": {
+ "type": "number"
+ },
+ "latestMessagesCount": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "pactPublications": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ },
+ "first": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "last": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "pactVersions": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "pacticipants": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "providerContractPublications": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "providerContractSelfVerifications": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "providerContractVersions": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "releasedVersions": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ },
+ "currentlySupportedCount": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "secrets": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "triggeredWebhooks": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "users": {
+ "additionalProperties": {},
+ "properties": {
+ "activeRegularCount": {
+ "type": "number"
+ },
+ "activeSystemCount": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "verificationResults": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ },
+ "failureCount": {
+ "type": "number"
+ },
+ "first": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "last": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "successCount": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "webhookExecutions": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ },
+ "webhooks": {
+ "additionalProperties": {},
+ "properties": {
+ "count": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "type": "object"
+ },
+ "name": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+}v0.40.0v0.34.0v0.27.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered without the description. The description adds nothing beyond that: it does not say whether the result is a single aggregate or a per-team breakdown, whether it respects any permission scoping, or anything about cost/latency, and the "Parameters: None" line merely restates the empty schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The single operative sentence is front-loaded and waste-free, but half the text is generator boilerplate ("**Toolset:** Metrics", "**Parameters:** None") that contributes nothing an agent can act on. It is appropriately short but not tight.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With zero parameters, a full annotation set and an output schema covering return values, the definition is close to sufficient. The remaining gap is the substance of the metric set and whether results are aggregated or per-team, which matters for deciding when this tool answers a question that get_metrics does not.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline of 4 applies. The explicit "None" note is consistent with the schema and at least confirms the absence of filters, though it is redundant.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ("Fetch metrics for all teams"), making the scope of the operation clear to an agent. It does not, however, differentiate itself from the sibling contract-testing_get_metrics, nor does it indicate which metrics are returned, so an agent cannot reliably choose between the two on description text alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no exclusion of alternatives, and no mention of prerequisites such as authentication or entitlement requirements. The only implicit signal is "all teams", which hints at an unscoped aggregate read, but nothing routes the agent between this and get_metrics.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.