Skip to main content
Glama

Council of AI GSPC

by io.github.CSOAI-ORG
OverviewDiscussionsAdmin

One GSPC board axis

get_axis
Read-onlyIdempotent

One axis row from the live GSPC board at https://councilof.ai/api/gspc — every axis the board carries, behavioural and financial families alike, addressed by the axis id exactly as the board spells it: n, accuracy, interval, MEASURED or UNMEASURED status, family, kind, the bank or run-artifact URL behind the row, and dates. An unmeasured axis is a first-class answer — a declared slot with no run behind it, published so the gap is visible — never an error and never a zero. Never a certification.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
axisYesThe axis name as it appears on the board, e.g. governance, safety, jail, provenance-controls. Case-insensitive. An unknown name returns the list of names the board actually carries.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNo
axisNo
stateYesLIVE, NOT_ON_BOARD, BAD_INPUT or UNREACHABLE
familyNo
leaderNo
sourceNo
statusNo
datasetNo
accuracyNo
intervalNo
measuredNo
board_carriesNo
resolved_fromNopresent when the caller named an alias (e.g. gov) that resolved to this board axis
not_a_certificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "accuracy": {},
+    "axis": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "board_carries": {
+      "type": "array"
+    },
+    "dataset": {},
+    "family": {},
+    "interval": {},
+    "leader": {},
+    "measured": {
+      "type": "boolean"
+    },
+    "n": {},
+    "not_a_certification": {
+      "type": "boolean"
+    },
+    "resolved_from": {
+      "description": "present when the caller named an alias (e.g. gov) that resolved to this board axis",
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "state": {
+      "description": "LIVE, NOT_ON_BOARD, BAD_INPUT or UNREACHABLE",
+      "type": "string"
+    },
+    "status": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "state"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "accuracy": {},
-    "axis": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "board_carries": {
-      "type": "array"
-    },
-    "dataset": {},
-    "family": {},
-    "interval": {},
-    "leader": {},
-    "measured": {
-      "type": "boolean"
-    },
-    "n": {},
-    "not_a_certification": {
-      "type": "boolean"
-    },
-    "resolved_from": {
-      "description": "present when the caller named an alias (e.g. gov) that resolved to this board axis",
-      "type": "string"
-    },
-    "source": {
-      "type": "string"
-    },
-    "state": {
-      "description": "LIVE, NOT_ON_BOARD, BAD_INPUT or UNREACHABLE",
-      "type": "string"
-    },
-    "status": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "state"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "accuracy": {},
+    "axis": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "board_carries": {
+      "type": "array"
+    },
+    "dataset": {},
+    "family": {},
+    "interval": {},
+    "leader": {},
+    "measured": {
+      "type": "boolean"
+    },
+    "n": {},
+    "not_a_certification": {
+      "type": "boolean"
+    },
+    "resolved_from": {
+      "description": "present when the caller named an alias (e.g. gov) that resolved to this board axis",
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "state": {
+      "description": "LIVE, NOT_ON_BOARD, BAD_INPUT or UNREACHABLE",
+      "type": "string"
+    },
+    "status": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "state"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already mark the tool read-only and idempotent, and the description adds rich behavioral context: unmeasured axes are valid first-class responses, not errors or zeros; unknown names return a list of board names; and responses come from a live board URL. There is no contradiction with the annotations.

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?

The description is front-loaded with the core operation and packs useful detail into three sentences. It is slightly dense in the middle, where the row fields follow the axis-id clause, but every part earns its place.

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

Completeness5/5

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

For a one-parameter read-only tool with an output schema and strong annotations, the description covers lookup behavior, edge cases such as unmeasured axes and unknown names, and the data source. Nothing an agent needs to correctly invoke it is missing.

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?

The input schema has 100% coverage for the sole parameter, including case-insensitivity and the unknown-name fallback. The description reinforces exact board spelling and the fields returned, but it does not materially change the parameter's meaning beyond what the schema already provides.

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?

The description opens with a concrete action and resource: returns one axis row from the live GSPC board. It lists the row's fields and clarifies that it is a single-axis lookup, not a board-level or card-level operation. The 'Never a certification' line further sharpens the tool's purpose.

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?

The description clearly establishes that this is a single-axis lookup by exact board id, but it does not name sibling alternatives or explicitly state when to choose this over board_totals, list_cards, or get_card. The 'Never a certification' line gives one negative boundary, so usage guidance is implied rather than explicit.

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

All Council of AI GSPC toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources