Skip to main content
Glama

Market Brew

Get task workload metrics

get_task_metrics
Read-onlyIdempotent

Use this when the user asks to get task workload 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_task_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.4/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 fully covered. The description does add one genuinely new behavioral fact: results are scoped to data visible to the linked Market Brew account, which hints at permission-based filtering. It says nothing about aggregation window, grouping, or response shape.

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

Conciseness3/5

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

Only two short sentences, so nothing is bloated, but the first sentence is near-redundant with the name and consumes the front-loaded position that should carry real purpose. The one substantive clause (account visibility) is buried second.

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 a "workload metric" actually contains — counts, per-crew breakdowns, date bucketing — and it does none of that. It also fails to differentiate from get_top_task_metrics despite near-identical naming.

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% and the nested query object documents its own filters (customerId, crewIds, websiteId, serverHost, startDate, endDate), so the schema does the heavy lifting. The description adds no meaning about how these filters combine or what the default range is. 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?

"Use this when the user asks to get task workload metrics" essentially restates the tool name and title without naming what metrics are returned or how they differ from the sibling get_top_task_metrics. The only added information is an account-visibility statement, which is not a statement of purpose.

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 trigger condition is circular: use this tool when the user asks for what this tool is named after. There is no mention of when not to use it, and no routing to the closely related get_top_task_metrics or get_task_history siblings.

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