Skip to main content
Glama

MetricDuck — Financial Analysis

by com.metricduck
OverviewDiscussionsAdmin

Guidance vs Actual

get_guidance_vs_actual
Read-only

Did management deliver what they guided? Joins forward guidance from earnings-call transcripts to reported actuals from 10-K/10-Q + 8-K earnings for the same ticker + fiscal period.

Returns both sides verbatim with quotes and locators.

Use Cases:

  • "Did NVDA deliver on Q2 FY2026 guidance?" -> get_guidance_vs_actual("NVDA", fiscal_period="Q2 FY2026")

  • "How disciplined has MSFT been against its own guidance?" -> get_guidance_vs_actual("MSFT") then compare across periods

  • "Latest period's guidance-vs-actual" -> get_guidance_vs_actual("TSLA") (period defaults to most recent)

Returns everything a beat/miss verdict needs — never the verdict: the comparison is basis-matched, as-reported arithmetic, and whether "above guidance" is good is the caller's judgment.

Output:

  • Guidance: forward items targeting the period — from earnings-call transcripts AND 8-K earnings releases (metric, value/range, basis, period, verbatim quote, source).

  • Actuals: SEC 10-Q/K metric + narrative signals for that period, plus 8-K earnings signals when present.

  • Comparison: for each guidance item, when it can be recomputed from the receipts on its OWN basis (GAAP vs non-GAAP matched, units aligned, period settled) — a neutral range_position (above | within | below the guided band) + signed delta. Otherwise a typed status says why NOT (no_actual_on_basis / not_yet_settled / value_unparsed / period_unresolved / value_incongruent) — never a false or guessed verdict. A non-GAAP guide is never compared to a GAAP actual.

  • Notes: calls/filings covered + comparison statuses, so you know coverage depth before interpreting.

Not point-in-time: the join uses everything stored today; for as-of work use a tool that takes vantage_date (e.g. get_earnings, get_financials).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesCompany ticker symbol (e.g., 'NVDA'). Must be exact.
fiscal_periodNoTarget fiscal period, e.g. "Q2 FY2026". If omitted, defaults to the most recent period with SEC filing actuals, or to a newer quarter whose 8-K earnings release is out when guidance targets it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fiscal_period / description
      Previous value: -"Target fiscal period, e.g. \"Q2 FY2026\". If omitted, defaults to the most recent period with SEC filing actuals."New value: +"Target fiscal period, e.g. \"Q2 FY2026\". If omitted, defaults to the most recent period with SEC filing actuals, or to a newer quarter whose 8-K earnings release is out when guidance targets it."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safe-read profile (readOnlyHint, destructiveHint=false), yet the description goes far beyond: it discloses basis-matching rules (non-GAAP never compared to GAAP), typed failure statuses (no_actual_on_basis, not_yet_settled, etc.), coverage notes, and the deliberate refusal to emit a verdict. It also flags the non-point-in-time join behavior, which annotations cannot convey.

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?

Front-loaded with the core question and organized into Use Cases / Output / caveat sections that are easy to scan. Slightly long and with some overlap between the opening 'returns both sides verbatim' line and the Output bullets, but nearly every sentence carries distinct information.

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, so the description carries the full burden of describing return shape, and it does so thoroughly: guidance items, actuals, comparison with range_position/delta or typed status, and coverage notes. An agent has everything needed to call and interpret this tool.

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%, so baseline is 3, but the description adds real meaning: it explains how fiscal_period resolves when omitted (most recent SEC-filing period, or a newer quarter whose 8-K release targets it) and demonstrates usage in the examples. It does not add further syntax or format detail beyond that.

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 precise verb+resource: joining forward guidance from earnings-call transcripts to reported actuals from 10-K/10-Q and 8-K filings for the same ticker and fiscal period. It is clearly distinguishable from siblings like get_earnings and get_financials, which it explicitly contrasts on the point-in-time dimension.

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

Usage Guidelines5/5

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

Provides three concrete use cases with example invocations, explains the fiscal_period default, and names the alternatives to use for as-of/point-in-time work (get_earnings, get_financials with vantage_date). When-to-use and when-not-to-use are both explicit.

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

All MetricDuck — Financial Analysis 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