list_rulesPaginated newest-first listing of the caller's own rules. Tier: sp500+ (sample rejected).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| cursor | No | Pagination cursor from a previous response's next_cursor. |
| Name | Required | Description | Default |
|---|---|---|---|
| _meta | Yes | Provenance envelope — data lineage for every MCP response | |
| rules | Yes | ||
| next_cursor | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / properties / rules / items / properties / action_params / anyOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "team_id": {
- "description": "A standing_agent.id identifying which team to run — same identifier shape as an alert's agent_run channel target.",
- "maxLength": 64,
- "minLength": 1,
- "type": "string"
- },
- "type": {
- "const": "run_team",
- "type": "string"
- }
- },
- "required": [
- "type",
- "team_id"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "channel": {
- "anyOf": [
- {
- "additionalProperties": false,
- "properties": {
- "hmac_secret": {
- "type": "string"
- },
- "target": {
- "format": "email",
- "maxLength": 256,
- "type": "string"
- },
- "type": {
- "const": "email",
- "type": "string"
- }
- },
- "required": [
- "type",
- "target"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "hmac_secret": {
- "description": "HMAC secret (≥16 chars) for webhook signature verification. Recommended for production.",
- "maxLength": 128,
- "minLength": 16,
- "type": "string"
- },
- "target": {
- "format": "uri",
- "maxLength": 512,
- "type": "string"
- },
- "type": {
- "const": "webhook",
- "type": "string"
- }
- },
- "required": [
- "type",
- "target"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "target": {
- "default": "@self",
- "description": "Always '@self' for dashboard channels. Routes to the in-app inbox keyed by the alert's owning customer.",
- "maxLength": 16,
- "type": "string"
- },
- "type": {
- "const": "dashboard",
- "type": "string"
- }
- },
- "required": [
- "type"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "target": {
- "description": "Slack incoming-webhook URL — must be on host hooks.slack.com (e.g. https://hooks.slack.com/services/T0000/B0000/XXXX). The URL itself is the secret, so no HMAC is used.",
- "format": "uri",
- "maxLength": 512,
- "type": "string"
- },
- "type": {
- "const": "slack",
- "type": "string"
- }
- },
- "required": [
- "type",
- "target"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "target": {
- "description": "A standing_agent.id identifying which standing agent team to run when this alert fires. NOT a URL — no outbound-URL validation applies to this field.",
- "maxLength": 64,
- "minLength": 1,
- "type": "string"
- },
- "type": {
- "const": "agent_run",
- "type": "string"
- }
- },
- "required": [
- "type",
- "target"
- ],
- "type": "object"
- }
- ],
- "description": "Delivery channel — same discriminated union create_alert accepts (email/webhook/dashboard/slack/agent_run)."
- },
- "message": {
- "description": "Optional custom message; defaults to a summary of the trigger event.",
- "maxLength": 2000,
- "minLength": 1,
- "type": "string"
- },
- "type": {
- "const": "send_alert",
- "type": "string"
- }
- },
- "required": [
- "type",
- "channel"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "params": {
- "additionalProperties": {},
- "description": "reverse_dcf DCF params — see create_report's own schema.",
- "type": "object"
- },
- "report_type": {
- "enum": [
- "reverse_dcf",
- "thesis"
- ],
- "type": "string"
- },
- "thesis_id": {
- "description": "Required when report_type=thesis.",
- "maxLength": 64,
- "minLength": 1,
- "type": "string"
- },
- "ticker": {
- "description": "Required when report_type=reverse_dcf.",
- "maxLength": 10,
- "minLength": 1,
- "type": "string"
- },
- "title": {
- "maxLength": 200,
- "minLength": 1,
- "type": "string"
- },
- "type": {
- "const": "create_report",
- "type": "string"
- }
- },
- "required": [
- "type",
- "report_type"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "as_of": {
- "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
- "type": "string"
- },
- "thesis_id": {
- "maxLength": 64,
- "minLength": 1,
- "type": "string"
- },
- "type": {
- "const": "score_thesis",
- "type": "string"
- }
- },
- "required": [
- "type",
- "thesis_id"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "context": {
- "additionalProperties": {},
- "type": "object"
- },
- "task": {
- "maxLength": 500,
- "minLength": 1,
- "type": "string"
- },
- "type": {
- "const": "schedule_task",
- "type": "string"
- },
- "wake_in_days": {
- "exclusiveMinimum": 0,
- "maximum": 90,
- "type": "number"
- }
- },
- "required": [
- "type",
- "task",
- "wake_in_days"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "message": {
- "maxLength": 2000,
- "minLength": 1,
- "type": "string"
- },
- "title": {
- "maxLength": 120,
- "minLength": 1,
- "type": "string"
- },
- "type": {
- "const": "post_inbox",
- "type": "string"
- }
- },
- "required": [
- "type",
- "title",
- "message"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "team_id": {
+ "description": "A standing_agent.id identifying which team to run — same identifier shape as a signal's agent_run channel target.",
+ "maxLength": 64,
+ "minLength": 1,
+ "type": "string"
+ },
+ "type": {
+ "const": "run_team",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "team_id"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "channel": {
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "hmac_secret": {
+ "type": "string"
+ },
+ "target": {
+ "format": "email",
+ "maxLength": 256,
+ "type": "string"
+ },
+ "type": {
+ "const": "email",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "target"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "hmac_secret": {
+ "description": "HMAC secret (≥16 chars) for webhook signature verification. Recommended for production.",
+ "maxLength": 128,
+ "minLength": 16,
+ "type": "string"
+ },
+ "target": {
+ "format": "uri",
+ "maxLength": 512,
+ "type": "string"
+ },
+ "type": {
+ "const": "webhook",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "target"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "target": {
+ "default": "@self",
+ "description": "Always '@self' for dashboard channels. Routes to the in-app inbox keyed by the signal's owning customer.",
+ "maxLength": 16,
+ "type": "string"
+ },
+ "type": {
+ "const": "dashboard",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "target": {
+ "description": "Slack incoming-webhook URL — must be on host hooks.slack.com (e.g. https://hooks.slack.com/services/T0000/B0000/XXXX). The URL itself is the secret, so no HMAC is used.",
+ "format": "uri",
+ "maxLength": 512,
+ "type": "string"
+ },
+ "type": {
+ "const": "slack",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "target"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "target": {
+ "description": "A standing_agent.id identifying which standing agent team to run when this signal fires. NOT a URL — no outbound-URL validation applies to this field.",
+ "maxLength": 64,
+ "minLength": 1,
+ "type": "string"
+ },
+ "type": {
+ "const": "agent_run",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "target"
+ ],
+ "type": "object"
+ }
+ ],
+ "description": "Delivery channel — same discriminated union create_signal accepts (email/webhook/dashboard/slack/agent_run)."
+ },
+ "message": {
+ "description": "Optional custom message; defaults to a summary of the trigger event.",
+ "maxLength": 2000,
+ "minLength": 1,
+ "type": "string"
+ },
+ "type": {
+ "const": "send_alert",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "channel"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "params": {
+ "additionalProperties": {},
+ "description": "reverse_dcf DCF params — see create_report's own schema.",
+ "type": "object"
+ },
+ "report_type": {
+ "enum": [
+ "reverse_dcf",
+ "thesis"
+ ],
+ "type": "string"
+ },
+ "thesis_id": {
+ "description": "Required when report_type=thesis.",
+ "maxLength": 64,
+ "minLength": 1,
+ "type": "string"
+ },
+ "ticker": {
+ "description": "Required when report_type=reverse_dcf.",
+ "maxLength": 10,
+ "minLength": 1,
+ "type": "string"
+ },
+ "title": {
+ "maxLength": 200,
+ "minLength": 1,
+ "type": "string"
+ },
+ "type": {
+ "const": "create_report",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "report_type"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "as_of": {
+ "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+ "type": "string"
+ },
+ "thesis_id": {
+ "maxLength": 64,
+ "minLength": 1,
+ "type": "string"
+ },
+ "type": {
+ "const": "score_thesis",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "thesis_id"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "context": {
+ "additionalProperties": {},
+ "type": "object"
+ },
+ "task": {
+ "maxLength": 500,
+ "minLength": 1,
+ "type": "string"
+ },
+ "type": {
+ "const": "schedule_task",
+ "type": "string"
+ },
+ "wake_in_days": {
+ "exclusiveMinimum": 0,
+ "maximum": 90,
+ "type": "number"
+ }
+ },
+ "required": [
+ "type",
+ "task",
+ "wake_in_days"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "message": {
+ "maxLength": 2000,
+ "minLength": 1,
+ "type": "string"
+ },
+ "title": {
+ "maxLength": 120,
+ "minLength": 1,
+ "type": "string"
+ },
+ "type": {
+ "const": "post_inbox",
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "title",
+ "message"
+ ],
+ "type": "object"
+ }
+]Output schema / properties / _meta / properties / fundamentals_as_ofAdded value: +{
+ "description": "ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to.",
+ "type": "string"
+}Output schema / properties / _meta / properties / price_as_ofAdded value: +{
+ "description": "ISO timestamp when the price surfaces were last refreshed.",
+ "type": "string"
+}Output schema / properties / _meta / properties / cost_usdAdded value: +{
+ "additionalProperties": false,
+ "description": "Per-call cost transparency. Omitted for subscription-only tools that have no PAYG-equivalent price.",
+ "properties": {
+ "amount_usd": {
+ "minimum": 0,
+ "type": "number"
+ },
+ "basis": {
+ "description": "payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed.",
+ "enum": [
+ "payg_charge",
+ "payg_rate_card"
+ ],
+ "type": "string"
+ },
+ "billed": {
+ "description": "true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free.",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "amount_usd",
+ "billed",
+ "basis"
+ ],
+ "type": "object"
+}Output schema / properties / _meta / properties / latency_msAdded value: +{
+ "description": "Wall-clock milliseconds this tool call took, measured server-side around the handler.",
+ "minimum": 0,
+ "type": "integer"
+}Output schema / properties / rules / items / properties / trigger_wiring_statusAdded value: +{
+ "description": "'live' means a real event source calls evaluateRulesForEvent() for this trigger_type today — this rule CAN fire. 'not_yet_wired' means the trigger_type is accepted and persisted for forward-compatibility but no code path dispatches it yet — this rule will never fire until Valuein wires that trigger source. Check this before relying on a rule; use alert_fired/inbox_item/scheduled_task_wake/schedule_tick for a rule that fires today.",
+ "enum": [
+ "live",
+ "not_yet_wired"
+ ],
+ "type": "string"
+}Output schema / properties / rules / items / requiredPrevious value: -[
- "id",
- "name",
- "trigger_type",
- "trigger_params",
- "condition_expr",
- "action_type",
- "action_params",
- "enabled",
- "last_fired_at",
- "fire_count",
- "created_at"
-]New value: +[
+ "id",
+ "name",
+ "trigger_type",
+ "trigger_params",
+ "condition_expr",
+ "action_type",
+ "action_params",
+ "enabled",
+ "last_fired_at",
+ "fire_count",
+ "created_at",
+ "trigger_wiring_status"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds behavioral details beyond the annotations: pagination, newest-first ordering, caller ownership, and the sp500+ tier restriction ('sample rejected'). These are valuable for the agent to understand how the tool behaves and what access is required.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core action, and every phrase adds meaningful information (pagination, ordering, scope, tier). No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 sufficiently covers key behavioral aspects: scope, ordering, pagination, and access tier. The tool is simple with only two optional parameters, and the description provides enough context for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description mentions pagination but does not detail limit/cursor semantics. However, the schema provides a clear description for cursor and constraints for limit, so parameters are partially documented. The description adds minimal additional meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states 'Paginated newest-first listing of the caller's own rules', defining the exact action, resource, and scope. It distinguishes from sibling tools by emphasizing 'caller's own' rules and noting the pagination and ordering.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage through the name and wording but does not explicitly contrast with alternatives or state when to use this tool over others. The 'caller's own' scope provides some context, but no when-not-to-use guidance is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose with detailed descriptions that clarify differences. Overlaps like get_peer_comparables vs screen_universe are well-differentiated by scope (single company vs cross-sectional). Similarly, get_insider_sentiment vs get_smart_money_flow are clearly distinguished by data sources and methodology.
All tool names follow a consistent verb_noun snake_case pattern (e.g., create_report, get_financial_ratios, delete_alert). No mixing of conventions or inconsistent verbs.
With 69 tools, the count far exceeds the 25+ threshold for 'too many'. While the domain is broad, the sheer volume likely overwhelms agents and increases selection complexity.
The tool set covers a wide range of SEC filings, ratios, smart-money data, alerts, reports, and more. Minor gaps exist (e.g., no options or detailed debt data), but most analyst workflows are supported.