Skip to main content
Glama

Market Brew

Count visible Crew accounts

count_crew
Read-onlyIdempotent

Use this when the user asks to count visible Crew accounts. 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": "count_crew"
  }
}

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. Changed8 schema fields changed
    • changedInput schema / properties / query / properties / customerId / 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"
      +  }
      +]
    • 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])))$"
    • removedInput schema / properties / query / properties / websiteId / $ref
      Removed value: -"#/properties/query/properties/customerId"
    • addedInput schema / properties / query / properties / websiteId / anyOf
      Added value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,17}$",
      +    "type": "string"
      +  }
      +]
  2. 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"
      +  }
      +}
  3. First observed

TDQS

B3.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's one real addition is the visibility constraint ('returns only data visible to the linked Market Brew account'), which usefully tells the agent results are account-scoped. It adds nothing else — no hint about what the returned count represents or how filters affect it.

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, front-loaded with the trigger condition and zero filler. Slight deduction because the second sentence opens with 'Returns only data' for a tool whose return is a count, which is marginally imprecise phrasing.

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

Completeness3/5

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

For a filtered-count tool with no output schema, the definition never indicates the return shape (a bare number versus a per-crew breakdown), which is the main thing an agent can't infer. With annotations carrying safety and the schema fully documenting filters, the remaining gap is modest but real.

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 six optional filters (customerId, crewIds, websiteId, serverHost, startDate, endDate). The description adds no meaning beyond that, so the baseline of 3 for a fully documented schema is appropriate.

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

Purpose4/5

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

States a specific verb and resource ('count visible Crew accounts'), which is unambiguous and clearly distinct from siblings like get_crew or get_current_crew (retrieval vs. counting) and from count_* siblings scoped to other resources. It stops short of explicitly naming an alternative, but the operation itself is unmistakable.

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

Usage Guidelines3/5

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

'Use this when the user asks to count visible Crew accounts' is an explicit trigger condition, which is better than nothing. However, it essentially restates the purpose rather than giving genuine routing guidance — no when-not conditions, no mention of when to prefer get_crew/list_crew_websites, and no note on whether filters are required or optional.

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