Velarion Company Intelligence

Generate a governance alpha card

generate_governance_alpha_card

Read-onlyIdempotent

Generate a Governance Alpha Card for a company.

Composite deterministic card: pay alignment (Velarion's own P4P-style estimate, modeled on public peer-advisory methodology concepts — not licensed ISS data), governance scorecard, SoP risk band, peer quality, top risks/strengths. Requires the company to be in Velarion's coverage universe with current-period data.

This tool was built as the free sample of the GOVERNANCE-ALPHA-CARD product. The owner killed that product (chat, 2026-09-24, verbatim "kill 15 through 41 … keep those 3"; docs/orders/ORDER_20260924_NON_AD7_KILL.md), so there is no longer a paid card to sample and no purchase path to offer. THE FREE TOOL STAYS (the order keeps every free page and free tool; only the buy option goes). Each agent may draw a limited number of cards per UTC day; beyond that the tool returns free_tier_cap_reached and nothing to buy.

Structured errors returned (not raised) for:

not_in_coverage: ticker outside the covered universe
not_deliverable: the company's current-period disclosure does not support a card
free_tier_cap_reached: daily free allowance spent (wait for 00:00 UTC)

Input Schema

TableJSON Schema

Name	Required	Description
`year`	No	Optional fiscal year to read (e.g. 2025). Defaults to the latest on file.
`ticker`	Yes	The company's ticker symbol (e.g. "AAPL").
`agent_token`	No	Optional Velarion agent token; falls back to the X-Velarion-Agent-Token header.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`status`	No	e.g. deliverable, free_tier_cap_reached.
`ticker`	No
`risk_band`	No
`attribution`	No	Source citation, dataset DOI, and a ready-made cite_as string.
`governance_scorecard`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 19, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "ticker"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

removedOutput schema / required
```
Removed value: -[
-  "ticker"
-]
```

First observedSep 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds valuable behavioral context: it is deterministic, returns structured errors rather than raising exceptions, and enforces a daily free-tier cap. It also clarifies that no purchase path exists, which is beyond the annotations. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and components, but it includes a lengthy product-history paragraph (order references, chat quotes) that is tangential to tool invocation. While this context clarifies that there is no purchase option, it could be condensed. The error list is useful but the overall text is not optimally concise.

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?

Given that an output schema exists (has_output_schema=true), the description appropriately does not explain return values. It covers coverage prerequisites, deliverability conditions, error behavior, and the daily cap. It is sufficiently complete for an agent to know when and how to call the tool, including failure modes. Minor gap: it does not explain how the card's components are interpreted, but that is likely in the output schema.

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%, so the schema already documents all three parameters (ticker, year, agent_token). The description adds minimal semantic value: it mentions coverage requirements and default year behavior, but these are already implied by the schema. The description does not significantly enhance parameter understanding beyond the schema.

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 clearly states the tool generates a 'Governance Alpha Card' and enumerates its composite components (pay alignment, governance scorecard, SoP risk band, peer quality, top risks/strengths). The verb+resource is specific and distinct from sibling tools that fetch raw compensation data or single metrics, so an agent can immediately understand what this tool produces.

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

Usage Guidelines3/5

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

The description provides prerequisites (coverage universe, current-period data) and a usage cap (free_tier_cap_reached), which are helpful. However, it does not explicitly contrast this tool with alternatives like get_company_compensation or predict_say_on_pay_risk, nor state when to prefer this composite card over those. The guidance is implicit rather than explicit.

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

All Velarion Company Intelligence 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.

Resources

Need Help?