Skip to main content
Glama
Sign In
joinwell52-AI

fcop-mcp

by joinwell52-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_issues

Retrieve validated canonical issue facts with deterministic severity, sender, and subject filters plus pagination to inspect and coordinate project issues.

Instructions

List validated canonical ISSUE facts, with deterministic filtering and pagination.

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
senderNo
severityNo
subject_refNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv4.0.5
    • removedInput schema / properties / lang
      Removed value: -{
-  "default": "",
-  "description": "Kept for 0.5.4 parity; currently unused.",
-  "type": "string"
-}
    • addedInput schema / properties / limit / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / limit / default
      Previous value: -0New value: +null
    • removedInput schema / properties / limit / description
      Removed value: -"Maximum number of rows (0 = no limit)."
    • removedInput schema / properties / limit / type
      Removed value: -"integer"
    • removedInput schema / properties / offset / description
      Removed value: -"Number of rows to skip."
    • removedInput schema / properties / reporter
      Removed value: -{
-  "default": "",
-  "description": "Filter by reporter role code (case-insensitive).",
-  "type": "string"
-}
    • addedInput schema / properties / sender
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / severity / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / severity / default
      Previous value: -""New value: +null
    • removedInput schema / properties / severity / description
      Removed value: -"Filter by severity (``critical`` / ``high`` /\n``medium`` / ``low``). Empty = all."
    • removedInput schema / properties / severity / type
      Removed value: -"string"
    • addedInput schema / properties / subject_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv3.2.4

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Deterministic filtering and pagination' hints at stable ordering, but it doesn't specify default ordering, maximum limit, whether omitted filters mean 'all', or what 'validated canonical' implies about data freshness.

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?

A single front-loaded sentence with no wasted clauses. It is efficiently sized, though its brevity is partly the source of the other gaps.

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?

Five undocumented parameters, no annotations, and no output schema leave the agent with little operational detail. For a filtered list endpoint, the description should at minimum clarify filter semantics and pagination defaults.

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

Parameters2/5

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

Schema description coverage is 0% for all five parameters, so the description must compensate. It only implies that sender/severity/subject_ref are filters and limit/offset are pagination, without explaining matching semantics, accepted severity values, or default behavior when filters are null.

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 (List) and resource (ISSUE facts), which distinguishes it from the task/report/review list siblings. 'Validated canonical facts' is jargon that adds little, but the core purpose 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 Guidelines2/5

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

No guidance on when to use this versus list_tasks, list_reports, or list_reviews, and no prerequisites or exclusions. The agent must infer usage purely from the resource name.

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