Skip to main content
Glama

Market Brew

Get aggregate system usage metrics

get_usage_metrics
Read-onlyIdempotent

Use this when the user asks to get aggregate system usage metrics. Returns only data visible to the linked Market Brew account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_usage_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional filters: customerId, crewIds (comma-separated numeric Crew IDs), websiteId, serverHost, startDate, and endDate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / query / additionalProperties
      Previous value: -{
      -  "type": [
      -    "string",
      -    "number",
      -    "boolean",
      -    "null"
      -  ]
      -}New value: +false
    • addedInput schema / properties / query / properties
      Added value: +{
      +  "crewIds": {
      +    "maxLength": 2048,
      +    "pattern": "^[1-9][0-9]*(,[1-9][0-9]*)*$",
      +    "type": "string"
      +  },
      +  "customerId": {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  },
      +  "endDate": {
      +    "$ref": "#/properties/query/properties/startDate"
      +  },
      +  "serverHost": {
      +    "maxLength": 253,
      +    "type": "string"
      +  },
      +  "startDate": {
      +    "format": "date",
      +    "type": "string"
      +  },
      +  "websiteId": {
      +    "$ref": "#/properties/query/properties/customerId"
      +  }
      +}
  2. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavior beyond that: results are scoped to data visible to the linked Market Brew account. It does not describe aggregation granularity, time-window defaults, or result shape.

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?

Two short sentences with no padding, and the account-scoping constraint is front-loaded. The first sentence, however, is pure tautology and does not earn its place.

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

Completeness2/5

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

There is no output schema, so the description carries the burden of explaining what comes back, yet it only states an access boundary and never characterizes the metric payload or its aggregation period. For a metrics-reporting tool with a nested filter object, this leaves the agent unable to predict or interpret results.

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?

There is a single optional `query` object, and the schema's own description already enumerates every filter (customerId, crewIds, websiteId, serverHost, startDate, endDate) at 100% coverage. The description adds no filter semantics, defaults, or interaction rules, so baseline 3 applies.

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

Purpose2/5

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

The sentence "Use this when the user asks to get aggregate system usage metrics" essentially restates the tool name and title rather than describing what the tool actually does. It never says which usage dimensions are aggregated (tasks, crews, API calls, licenses) nor how it differs from metric siblings such as get_search_metrics, get_crawl_metrics, or get_task_metrics.

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

Usage Guidelines2/5

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

The only guidance is a restatement of the request phrase that would trigger it, with no when-not conditions and no naming of alternative metrics tools. With ten-plus sibling metric tools present, the absence of routing guidance leaves selection entirely to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources