Skip to main content
Glama
Sign In

Fivebar Trading

by io.github.fivebar-xyz
OverviewDiscussionsAdmin

Stock due diligence report

stock_report
Read-only

Due diligence on a US-listed company beyond the last numbers, all from its SEC filings: the trend over eight quarters (revenue growth against the same quarter a year before, gross, operating and net margins, inventory or receivables outgrowing sales, free cash flow against earnings), valuation (market cap, P/E, P/S from its Robinhood stock token price, when it has one), management's outlook quoted from the latest earnings release, the 8-Ks of the last 120 days (CEO changes, auditor changes, restatements, layoffs), dated catalysts ahead (the next earnings date estimated from last year's, debt coming due, buyback left, shelf expiry, annual meeting), and what to watch (risk factors added in the latest 10-K, customer concentration, going-concern language). Each item links to its filing. Use for 'do DD on X', 'what are the catalysts for X', 'what should I watch on X'. Premium: 10¢ a call from prepaid agent credits (3 free premium calls a day). Send your agent key as Authorization: Bearer .

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": {
      "company": "<company>"
    },
    "name": "stock_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesTicker (MU), company name, or SEC CIK

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds material context the annotations cannot: it is a paid premium call at 10¢ with 3 free calls per day, requires an agent key passed as 'Authorization: Bearer <key>', sources everything from SEC filings, and links each item back to its filing. Cost and auth requirements are exactly the operational facts 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.

Conciseness3/5

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

Front-loaded with the core purpose, and the pricing/auth line is well placed at the end, but the middle is one very long run-on sentence enumerating a dozen deliverables that would read far better as a structured list. Almost all content earns its place, but the density hurts scanability.

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?

There is no output schema, yet the description fully itemizes what comes back, plus cost, free-tier, and auth mechanics. For a single-parameter research tool, nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single 'company' parameter, so baseline is 3. The description adds scope meaning beyond the schema: the subject must be a US-listed company with SEC filings, which tells the agent the input domain is constrained to SEC-registered issuers. No format examples beyond the schema's own 'MU' example.

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?

States a specific verb+resource (due diligence on a US-listed company from SEC filings) and enumerates the concrete outputs: eight-quarter trends, valuation, management outlook, 8-Ks, catalysts, risk factors. The phrase 'beyond the last numbers' implicitly separates it from the quote-style siblings, so an agent can tell what it adds over a price lookup.

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

Usage Guidelines4/5

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

Gives explicit trigger phrases ('do DD on X', 'what are the catalysts for X', 'what should I watch on X'), which is strong when-to-use guidance. It stops short of naming an alternative sibling or stating when-not to use it (e.g. for a plain quote or a raw filing search), so it does not reach the top band.

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

All Fivebar Trading 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