Gemral Edge

Actor Habit Profile

get_actor_profile

Deep profiling of individual lawmakers, agencies, and defense contractors including multi-year trade win-rates, committee jurisdictions, and legislative actions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "actor_id": "<actor_id>"
    },
    "name": "get_actor_profile"
  }
}

Input Schema

Name	Required	Description	Default
`actor_id`	Yes	Politician congressional member ID or Executive slug/CIK
`actor_type`	No		politician

Output Schema

Name	Required	Description
`notice`	No	Free-tier upgrade notice; only when results are masked/delayed.
`results`	Yes	Tool result payload (read-only evidence). Shape varies by tool; scoring weights are never exposed.
`history_limit`	No	Present when the license limits history depth: earliest_allowed date, history_days and how many older items were removed.
`deprecated_fields`	No	Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / deprecated_fields

Added value: +{
+  "description": "Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 23, 2026

changedInput schema / properties / actor_id / description

Previous value: -"Politician BioGuide ID or Executive slug/CIK"New value: +"Politician congressional member ID or Executive slug/CIK"

First observedOct 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false, which is surprising for a "get" tool and the description neither explains nor contradicts it. The description does add scope context (multi-year history, committee jurisdictions) but says nothing about cost, depth/latency, or why a profile retrieval is flagged as a non-read operation.

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?

A single dense sentence, front-loaded with the scope and then the returned dimensions. No filler, though the field list is a bit of a run-on.

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?

An output schema exists, so return values need not be explained; the description correctly spends its budget on scope and payload categories instead. The remaining gaps (routing, actor_type) are usage-level rather than reasons an agent would call it incorrectly.

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 coverage is 50%: actor_id is documented but actor_type is bare enum-only with a default. The description's mention of lawmakers, agencies, and contractors loosely hints at the actor_type values but omits activist_fund and insider and gives no guidance on how actor_type changes the lookup.

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 the resource (profiles of lawmakers, agencies, defense contractors) and enumerates the payload categories (win-rates, committee jurisdictions, legislative actions), which distinguishes it from narrower siblings like get_committee_conflict_map or search_accountability_people. The verb is nominal ("Deep profiling") rather than an explicit retrieval verb, so it is clear but not maximally crisp.

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 search_accountability_people (to find an actor) or get_committee_conflict_map / get_contract_beneficiaries (for narrower slices). The agent must infer routing from the return-field list alone.

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

All Gemral Edge 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.