Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

needfix_count

Read-only

Count NeedFix entries with optional kind, status, or severity filters, and return a breakdown by work state and status.

Instructions

Bounded count of NeedFix entries.

Use this for a single number; use needfix_list for the matching rows themselves. With breakdown=true the reply is {count, by_work_state, by_status, derived, underived_reason}: count is the same number, and the two maps split the same candidate rows by work state (untriaged, decided_no_card, in_work, stalled, reopened, deferred, closed) and by status.

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": "needfix_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoCount only rows of this exact kind, e.g. bug or improvement; any filter returns the raw row count instead of the derived active count.
statusNoCount only rows with this exact status, e.g. captured or accepted; archived rows are counted only when asked for here. Omit all three filters for the derived active count.
severityNoCount only rows of this exact severity: critical, high, medium, low or info; any filter returns the raw row count.
breakdownNoReturn {count, by_work_state, by_status} instead of the bare number; default false.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.98
    • addedInput schema / properties / breakdown
      Added value: +{
+  "default": false,
+  "description": "Return {count, by_work_state, by_status} instead of the bare number; default false.",
+  "title": "Breakdown",
+  "type": "boolean"
+}
    • addedOutput schema / properties / result / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]
    • removedOutput schema / properties / result / type
      Removed value: -"integer"
  2. Changed3 schema fields changedv0.12.67
    • addedInput schema / properties / kind / description
      Added value: +"Count only rows of this exact kind, e.g. bug or improvement; any filter returns the raw row count instead of the derived active count."
    • addedInput schema / properties / severity / description
      Added value: +"Count only rows of this exact severity: critical, high, medium, low or info; any filter returns the raw row count."
    • addedInput schema / properties / status / description
      Added value: +"Count only rows with this exact status, e.g. captured or accepted; archived rows are counted only when asked for here. Omit all three filters for the derived active count."
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the useful behavioral detail that the count is "bounded" and that breakdown=true changes the reply shape to a map-based structure. It stops short of describing pagination or limits on the bounded count, which keeps it from a 5.

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?

Front-loaded with the core purpose and the sibling contrast in the first two sentences. The breakdown sentence is dense but every clause carries information; minor cost is that it slightly duplicates the schema's breakdown description.

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

Completeness4/5

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

With an output schema present, return values need not be explained, yet the description still characterizes the breakdown payload. One small gap: the description lists derived/underived_reason in the breakdown reply while the schema's breakdown description lists only count/by_work_state/by_status, a minor inconsistency an agent may notice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by enumerating the work-state buckets (untriaged, decided_no_card, in_work, stalled, reopened, deferred, closed) and mentioning derived/underived_reason, which the schema does not spell out.

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

Purpose5/5

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

States a specific verb and resource ("Bounded count of NeedFix entries") and immediately contrasts with the sibling needfix_list, so an agent can pick between counting and listing without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says when to use this tool ("for a single number") and names the alternative (needfix_list) for the matching rows. It also flags the breakdown=true variant as the way to get grouped output, leaving no routing ambiguity.

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

Deploy Server

Other Tools