Skip to main content
Glama

Stockfacts

by io.github.AAAZZZR
OverviewDiscussionsAdmin

Politician (member of the U.S. Congress)

get_politician
Read-onlyIdempotent

One politician (a member of the U.S. Congress: House or Senate), by bioguide ID or name: party, chamber, state, district, in office or former, terms served with start and end dates; a profile with the official photo_url, position (e.g. U.S. Representative for California's 11th district), district code (CA-11), birthday and age, official website, social accounts and Wikipedia as URLs, leadership roles (Speaker, whips, caucus chairs; current first) and, for politicians in office, current committee and subcommittee seats with titles (chair, ranking_member and so on); trade statistics since 2020 for the chosen assets (listed securities by default: trades, buys, sells, estimated volume in USD, median filing delay in days, late trades and the reports that contain them), unlisted_trades (trades in bonds, private holdings and other assets, whatever asset is), the number of reports and how many are paper or scanned, the latest filing date, and the 5 tickers the politician traded most in the chosen assets, with livermore.club links. Use get_politician_trades with the bioguide ID for the trades. Profiles, committees and photos come from the unitedstates project (public domain), refreshed daily. Data: House and Senate periodic transaction reports (PTRs) filed since 2020-01-01, from the U.S. House Clerk and the Senate Office of Public Records (eFD), updated daily. Only listed securities are included by default: stocks (including ADRs), ETFs and options, the assets with an exchange ticker. Politicians also report Treasury bills and notes, municipal and corporate bonds, private companies, private funds, crypto and other assets; pass asset=other for those or asset=all for everything. Amounts are the statutory ranges members of Congress report, not exact values: amount_min_usd to amount_max_usd, where a null amount_max_usd is an 'Over $X' range; estimated volumes add up range midpoints (an 'Over $X' range counts as X), so treat them as rough sizes. Trades replaced by an amendment and duplicates reported again in a later filing are left out. Paper and scanned reports are listed on politician pages but their trades are not read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetNoWhich assets to include: listed (default) = listed securities, that is stocks including ADRs, ETFs and options; stock = listed stocks and ETFs without options; option = options; other = Treasury bills and notes, municipal and corporate bonds, private companies, private funds, crypto and other assets; all = everything. The statistics and top tickers cover these assets.listed
politicianYesA bioguide ID (e.g. P000197) or a name (e.g. Pelosi, Nancy Pelosi, Bernie Sanders). A name that matches several politicians returns an error listing them.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
noteYes
assetYesThe assets that stats and top_tickers cover.
statsYes
profileYes
politicianYes
top_tickersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / profile
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "age": {
+      "description": "Age today (US Eastern), for politicians in office only: the source has no date of death, so it is null for former members.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "birthday": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "committees": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "chamber": {
+            "description": "house, senate or joint.",
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "side": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "subcommittees": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "id": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                },
+                "side": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "title": {
+                  "anyOf": [
+                    {
+                      "enum": [
+                        "chair",
+                        "vice_chair",
+                        "ranking_member",
+                        "ex_officio",
+                        "co_chair",
+                        "other"
+                      ],
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ],
+                  "description": "chair, vice_chair, ranking_member, ex_officio, co_chair or other (the source's wording is in title_raw); null for a regular member."
+                },
+                "title_raw": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "required": [
+                "id",
+                "name",
+                "side",
+                "title",
+                "title_raw"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "title": {
+            "anyOf": [
+              {
+                "enum": [
+                  "chair",
+                  "vice_chair",
+                  "ranking_member",
+                  "ex_officio",
+                  "co_chair",
+                  "other"
+                ],
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "chair, vice_chair, ranking_member, ex_officio, co_chair or other (the source's wording is in title_raw); null for a regular member."
+          },
+          "title_raw": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "side",
+          "title",
+          "title_raw",
+          "chamber",
+          "url",
+          "subcommittees"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "district": {
+      "description": "House seat code of the latest term, e.g. CA-11; AK-AL for an at-large seat, DC-AL for a delegate; null for senators.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "leadership": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "chamber": {
+            "type": "string"
+          },
+          "current": {
+            "type": "boolean"
+          },
+          "end": {
+            "description": "The end date, or null when the source gives none (the role is held).",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "start": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "chamber",
+          "start",
+          "end",
+          "current"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "photo_url": {
+      "description": "Official portrait, 360x450 WebP, public domain; null when there is no photo.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "position": {
+      "description": "The seat in English, e.g. U.S. Representative for California's 11th district.",
+      "type": "string"
+    },
+    "social": {
+      "additionalProperties": false,
+      "properties": {
+        "facebook": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "instagram": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "mastodon": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "x": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "youtube": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "x",
+        "facebook",
+        "youtube",
+        "instagram",
+        "mastodon"
+      ],
+      "type": "object"
+    },
+    "website": {
+      "description": "Official website; politicians in office only.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "wikipedia_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "photo_url",
+    "position",
+    "district",
+    "birthday",
+    "age",
+    "website",
+    "social",
+    "wikipedia_url",
+    "leadership",
+    "committees"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "politician",
-  "asset",
-  "stats",
-  "top_tickers",
-  "note",
-  "url"
-]New value: +[
+  "politician",
+  "profile",
+  "asset",
+  "stats",
+  "top_tickers",
+  "note",
+  "url"
+]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety; the description adds data provenance, daily refresh, statutory amount ranges, treatment of amendments/duplicates, and paper/scanned reports not being read. These are substantive behavioral constraints beyond 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 a single dense block with semicolon-delimited clauses, front-loading identity and fields but running very long. Most content is relevant for this complex tool, though some output detail is redundant with the output schema.

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?

With an output schema present, the description need not explain returns, yet it goes beyond by covering data sources, refresh cadence, asset defaults, amount interpretation, and report limitations. Combined with annotations and 100% schema coverage, an agent has everything needed to call correctly.

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 100%, with both parameters fully documented including the asset enum. The description restates the default and asset meanings but adds no parameter-level syntax or 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 names the resource and scope precisely—one U.S. Congress member, by bioguide ID or name—and enumerates profile fields and trade statistics. It explicitly distinguishes this from get_politician_trades, so an agent can select it without inspecting siblings.

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

Usage Guidelines5/5

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

It states the alternative tool and the selector: use get_politician_trades with the bioguide ID for trades. It also defines asset parameter choices and default, giving context for when to fetch other asset classes. The alternative routing is explicit.

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

All Stockfacts 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