ko-mcp

get_congress_member

Read-onlyIdempotent

Get detailed trading history of a specific U.S. Congress member. Shows individual trades with transaction types, amounts, and disclosure dates.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No
`limit`	No
`member`	Yes	Member slug (e.g. 'nancy-pelosi', 'dan-crenshaw'). Use get_congress_trades or search to find exact slugs.

Output Schema

TableJSON Schema

Name	Required	Description
`rows`	Yes
`member`	Yes
`paging`	Yes	Paging state reconciled from ko.io meta.total_count and meta.softwall
`coverage`	Yes
`plan_limit`	Yes	The Free/keyless plan limits ko.io applied to this answer (null for paid callers)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 9, 2026

addedOutput schema / properties / coverage

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "note": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "paper_filings": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "paper_filings",
+        "note"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "member",
-  "rows",
-  "paging",
-  "plan_limit"
-]New value: +[
+  "member",
+  "coverage",
+  "rows",
+  "paging",
+  "plan_limit"
+]

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "member": {
+      "type": "string"
+    },
+    "paging": {
+      "additionalProperties": false,
+      "description": "Paging state reconciled from ko.io meta.total_count and meta.softwall",
+      "properties": {
+        "continuation": {
+          "description": "SIGNIN_REQUIRED = page>1 needs a (free) ko.io API key",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "has_more": {
+          "description": "null = a full page came back and more MAY exist",
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "next_page": {
+          "anyOf": [
+            {
+              "$ref": "#/properties/paging/properties/total_count/anyOf/0"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Next page THIS caller can open; null when there is none (or sign-in is required)"
+        },
+        "page": {
+          "type": "integer"
+        },
+        "per_page": {
+          "type": "integer"
+        },
+        "plan_row_cap": {
+          "anyOf": [
+            {
+              "$ref": "#/properties/paging/properties/total_count/anyOf/0"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Row cap the caller's plan applied to this page, if any"
+        },
+        "returned": {
+          "type": "integer"
+        },
+        "total_count": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Total rows matching the request, when ko.io reported it"
+        },
+        "truncated_by_plan": {
+          "description": "True when the plan's row cap withheld rows from this page",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "page",
+        "per_page",
+        "returned",
+        "total_count",
+        "has_more",
+        "next_page",
+        "continuation",
+        "plan_row_cap",
+        "truncated_by_plan"
+      ],
+      "type": "object"
+    },
+    "plan_limit": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "continuation": {
+              "$ref": "#/properties/rows/items/properties/member_name"
+            },
+            "date_basis": {
+              "$ref": "#/properties/rows/items/properties/member_name"
+            },
+            "effective_period": {
+              "$ref": "#/properties/rows/items/properties/member_name"
+            },
+            "policy_version": {
+              "$ref": "#/properties/rows/items/properties/member_name"
+            },
+            "row_cap": {
+              "anyOf": [
+                {
+                  "$ref": "#/properties/paging/properties/total_count/anyOf/0"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "truncated": {
+              "type": [
+                "boolean",
+                "null"
+              ]
+            },
+            "window_end": {
+              "$ref": "#/properties/rows/items/properties/member_name"
+            },
+            "window_start": {
+              "$ref": "#/properties/rows/items/properties/member_name"
+            }
+          },
+          "required": [
+            "policy_version",
+            "window_start",
+            "window_end",
+            "effective_period",
+            "date_basis",
+            "row_cap",
+            "truncated",
+            "continuation"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The Free/keyless plan limits ko.io applied to this answer (null for paid callers)"
+    },
+    "rows": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "amount_range": {
+            "description": "The disclosed dollar RANGE (STOCK Act bands), not an exact amount",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "asset_description": {
+            "$ref": "#/properties/rows/items/properties/member_name"
+          },
+          "chamber": {
+            "$ref": "#/properties/rows/items/properties/member_name"
+          },
+          "disclosure_date": {
+            "$ref": "#/properties/rows/items/properties/member_name"
+          },
+          "member_name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "owner": {
+            "$ref": "#/properties/rows/items/properties/member_name"
+          },
+          "ticker": {
+            "$ref": "#/properties/rows/items/properties/member_name"
+          },
+          "transaction_date": {
+            "$ref": "#/properties/rows/items/properties/member_name"
+          },
+          "transaction_type": {
+            "$ref": "#/properties/rows/items/properties/member_name"
+          }
+        },
+        "required": [
+          "member_name",
+          "chamber",
+          "ticker",
+          "asset_description",
+          "transaction_type",
+          "transaction_date",
+          "disclosure_date",
+          "amount_range",
+          "owner"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "member",
+    "rows",
+    "paging",
+    "plan_limit"
+  ],
+  "type": "object"
+}

First observedJul 11, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so safety is fully covered. The description adds value by enumerating the returned content (individual trades, transaction types, amounts, disclosure dates), but says nothing about pagination semantics of the page/limit controls or result volume, which is where the real behavioral ambiguity lies.

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 tight sentences, front-loaded with the core action, no filler. The second sentence partly restates output that the output schema already defines, which is mild redundancy, but it does orient the agent quickly.

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?

With an output schema and full annotations present, the description need not explain return values or safety, and it covers the basic action. It is nonetheless incomplete on two points an agent needs: differentiation from get_congress_trades and any indication of pagination/result-size behavior for a member with many trades.

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 only 33% — the member slug is documented in the schema, while page and limit have no descriptions at all (only defaults and bounds). The tool description supplies no compensating detail about pagination, slug format, or how results are ordered, so the coverage gap is left unaddressed.

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?

Names a specific verb and resource: 'Get detailed trading history of a specific U.S. Congress member', and reinforces it with the returned data shape (trades, transaction types, amounts, disclosure dates). It does not, however, distinguish itself from the sibling get_congress_trades, leaving the agent to infer that one is member-scoped and the other is not.

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?

The description contains no when-to-use, when-not-to-use, or alternative selection guidance. The only routing hint ('Use get_congress_trades or search to find exact slugs') lives in the member parameter's schema description, not in the tool description itself, so on description alone an agent cannot tell why it would pick this over get_congress_trades.

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

All ko-mcp tools Inspect

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.