Skip to main content
Glama

Market Brew

Get top-task metrics

get_top_task_metrics
Read-onlyIdempotent

Use this when the user asks to get top-task 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_top_task_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional filters: websiteId, serverHost, startDate, endDate, taskTitle, sortBy, sortDir, offset, and pageSize.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / query / properties / endDate / $ref
      Removed value: -"#/properties/query/properties/startDate"
    • addedInput schema / properties / query / properties / endDate / format
      Added value: +"date"
    • addedInput schema / properties / query / properties / endDate / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • addedInput schema / properties / query / properties / endDate / type
      Added value: +"string"
    • addedInput schema / properties / query / properties / startDate / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • changedInput schema / properties / query / properties / websiteId / anyOf
      Previous value: -[
      -  {
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "minimum": -9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "pattern": "^[1-9][0-9]{0,17}$",
      -    "type": "string"
      -  }
      -]New value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,17}$",
      +    "type": "string"
      +  }
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / query / additionalProperties
      Previous value: -{
      -  "type": [
      -    "string",
      -    "number",
      -    "boolean",
      -    "null"
      -  ]
      -}New value: +false
    • changedInput schema / properties / query / description
      Previous value: -"Optional filters: websiteId, serverHost, workspaceId, startDate, endDate, taskTitle, sortBy, sortDir, offset, and pageSize."New value: +"Optional filters: websiteId, serverHost, startDate, endDate, taskTitle, sortBy, sortDir, offset, and pageSize."
    • addedInput schema / properties / query / properties
      Added value: +{
      +  "endDate": {
      +    "$ref": "#/properties/query/properties/startDate"
      +  },
      +  "offset": {
      +    "maximum": 1000000,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  "pageSize": {
      +    "maximum": 200,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  "serverHost": {
      +    "maxLength": 253,
      +    "type": "string"
      +  },
      +  "sortBy": {
      +    "maxLength": 80,
      +    "type": "string"
      +  },
      +  "sortDir": {
      +    "enum": [
      +      "asc",
      +      "desc"
      +    ],
      +    "type": "string"
      +  },
      +  "startDate": {
      +    "format": "date",
      +    "type": "string"
      +  },
      +  "taskTitle": {
      +    "maxLength": 2048,
      +    "type": "string"
      +  },
      +  "websiteId": {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  }
      +}
  3. 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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds one genuine behavioral fact beyond that: results are scoped to the linked Market Brew account. It says nothing about pagination limits, result size, or what 'top' means, so the added value is modest.

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?

Two short sentences with no padding, so length is not a problem. However, the first sentence is pure tautology and consumes the front-loaded position that should carry the actual explanation, leaving the structure technically tight but substantively empty.

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?

This is a read-only analytics tool with a nested filter object, no output schema, and no explanation of the returned shape. Since no output schema exists, the description should explain what 'top-task metrics' contains and how ranking/paging behaves, and it does neither.

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 description coverage is 100% and the nested query object's own description enumerates all eight filters (websiteId, serverHost, dates, taskTitle, sorting, paging), so the schema carries the parameter burden. The description adds no meaning beyond it, which is acceptable at this coverage level but earns no credit above baseline.

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 description only restates the title: "Use this when the user asks to get top-task metrics." It never says what a top task is, what metrics are returned, or how the result differs from sibling tools like get_task_metrics and list_top_tasks. An agent cannot distinguish this tool's purpose from the name alone.

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 circular trigger phrase that echoes the tool name, with no when-to-use versus when-not-to-use criteria and no mention of the obvious alternatives (get_task_metrics, list_top_tasks). Nothing helps an agent choose between this and its near-duplicate 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