Skip to main content
Glama

State Vector Factor Loadings

sv_factors
Read-only

PCA factor loadings per ticker/date — 22-component regime decomposition (state_vector_pca panel). Params: ticker, start/end, limit. Free with X-ORKID-API-Key or $0.01 USDC/call via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sv_factors"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd date YYYY-MM-DD
limitNoMax rows, default 100, cap 500
panelNoPanel to query (default first). Available: state_vector_pca
startNoStart date YYYY-MM-DD
tickerNoTicker, e.g. "AAPL"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description goes beyond them by disclosing both authentication/cost paths (X-ORKID-API-Key or $0.01 USDC per call via x402), which is real operational context an agent needs before invoking.

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?

Three short front-loaded segments: what the data is, its parameters, and its cost. The parameter listing partially duplicates the schema, which is the only wasted space; otherwise there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has five optional parameters and no output schema, so the description carries the burden of explaining what a returned row contains. It names the dataset but never describes the shape of a factor-loading record or pagination behavior beyond the limit cap already in the 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 five parameters including defaults and the 500-row cap. The description lists ticker, start/end and limit and ties the panel to state_vector_pca, adding marginal clarification but no format or usage detail beyond the schema.

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 a concrete resource (PCA factor loadings) with scope (per ticker/date), dimensionality (22-component) and the backing panel (state_vector_pca). That is enough to distinguish it from most siblings, but it never explicitly contrasts with sv_vectors or sv_cot, which an agent may conflate with it.

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?

There is no when-to-use guidance, no exclusions, and no named alternative. The description enumerates parameters but never says under what circumstances an agent should pick this tool over sv_vectors or the other state-vector siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources