Skip to main content
Glama
Sign In
joinwell52-AI

fcop-mcp

by joinwell52-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_reports

List reports with filtering by sender, subject, attempt, and head-only selection, enabling retrieval of exact coordination records for multi-agent workflows.

Instructions

List REPORTs through Core, including exact attempt and head selection semantics.

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
senderNo
head_onlyNo
attempt_idNo
subject_refNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv4.0.5
    • addedInput schema / properties / attempt_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / head_only
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
    • 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
+}
    • removedInput schema / properties / status
      Removed value: -{
-  "default": "open",
-  "description": "``open`` (default), ``archived``, or ``all``.",
-  "type": "string"
-}
    • addedInput schema / properties / subject_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • removedInput schema / properties / task_id
      Removed value: -{
-  "default": "",
-  "description": "Filter by source task ID.",
-  "type": "string"
-}
    • 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.6/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 and doesn't meet it. It says nothing about pagination behavior, ordering, default filtering when sender/attempt_id/subject_ref are null, or what 'head selection' actually means operationally.

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?

It is a single front-loaded sentence, so it isn't verbose, but the phrase 'including exact attempt and head selection semantics' spends words on unhelpful jargon rather than conveying information.

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?

With 6 mostly optional filter/pagination parameters, zero schema description coverage, no annotations, and no output schema, one sentence is insufficient to call this tool correctly. Nothing explains default result sets or the meaning of the head/attempt selection modes.

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% across 6 parameters, and the description only makes a vague gesture toward 'attempt' and 'head' semantics without explaining limit, offset, sender, attempt_id, subject_ref, or head_only. An agent still cannot tell what head_only=true does or how the filter parameters interact.

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 ('List REPORTs'), which clearly distinguishes it from read_report and write_report among the siblings. However, 'through Core' and 'exact attempt and head selection semantics' are unexplained jargon that doesn't sharpen the 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?

No guidance on when to use this versus read_report or list_issues/list_reviews, and no prerequisites or exclusions stated. The agent must infer usage purely from the 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