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
`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.

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

A3.6/5.0

Behavior3/5

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

Annotations fully declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety aspects. The description adds that the tool shows trading history details, which is helpful. However, it does not disclose behavioral aspects like pagination behavior, rate limits, or how the 'page' and 'limit' parameters affect results. Since annotations cover the safety profile, a 3 is appropriate.

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 a single sentence, concise and directly states what it does. It is front-loaded with the purpose ('Get detailed trading history'), and the rest adds detail. No wasted words, though it could mention usage context for siblings, but that is not strictly necessary.

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?

The tool has an output schema available (which likely details return format), and annotations cover read-only behavior. The description explains what the tool returns (trades with transaction types, amounts, dates). It does not explain the 'member' slug format or how to find it, but that is covered in the schema's parameter description. Given the output schema and annotations, the description is adequate for the agent to know what to expect.

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?

Schema description coverage is only 33%, meaning the description for 'member' parameter exists, but 'page' and 'limit' lack descriptions. The main description does not clarify the meaning of 'page' and 'limit', relying on the schema's defaults and types. The description adds context for 'member' (that it is a slug) but not for the other parameters. With low coverage, the description does not fully compensate, but the schema provides enough via names and types.

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?

The description clearly states a specific verb ('Get') and resource ('trading history of a specific U.S. Congress member'), and specifies what is shown (individual trades with transaction types, amounts, disclosure dates). This distinguishes it from the sibling 'get_congress_trades' which likely lists all trades, though it does not explicitly name the sibling. The purpose is clear and unambiguous.

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

Usage Guidelines4/5

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

The description implies usage context: it is for retrieving details on a specific congress member, while the sibling 'get_congress_trades' likely provides a broader listing. However, it does not explicitly state when NOT to use this tool or name alternatives. The parameter schema hint 'Use get_congress_trades or search to find exact slugs' partially guides usage, but that is in the parameter description, not the main description.

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.