pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for optionsahoy-mcp

Pod holds 16 of 29 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to optionsahoy-mcp.

Most discussed

qsbs_check: Parameters 3/5 → 5/5 (description must add semantic meaning beyond 100%-covered schema)

Tool: qsbs_check (functions/_lib/mcp-tools.ts:284) Dimension: Parameters Current score: 3/5 (capped at baseline 3 because schema coverage is already 100%) Target: 5/5

Glama TDQS feedback (verbatim, v1.2.2 re-eval)

Schema description coverage is 100%, so baseline is 3. The schema's parameter descriptions are already very detailed (explaining each test, allowed values, etc.). The description adds an important note about not inventing values for required fields, but does

Read the thread · 2026-05-29 · closed · 2 comments

nso_calculate: Conciseness 3/5 → 5/5 (tighten + structure return-keys block)

TDQS gap

Glama Tool Definition Quality Score on v1.2.4:

  • nso_calculate Conciseness: 3/5 (lowest dimension on the lowest-scoring tool, tied at 4.6/5)

Quoting the rubric's judgment:

The description is comprehensive but somewhat verbose, with multiple sentences that could be tightened. It is front-loaded with purpose and usage, but the detail on return keys and constraints could be more structured.

Current per-tool board

| Dimension | Now | Target | |-----------------|-----

Read the thread · 2026-05-29 · closed · 1 comment

protective_put_price: Parameters 4/5 → 5/5 (add parameter-interaction semantics)

TDQS gap

Glama Tool Definition Quality Score v1.2.3 evaluation:

  • protective_put_price Parameters: 4/5

Quoting the rubric's judgment:

Schema coverage is 100% with descriptions for each parameter. The description adds extra meaning: for volatility it warns against inventing a value and explains fallback; for sector it mentions the lookup table source; for protectionLevel it explains the strike formula. This goes beyond the schema, but some extra details are also present in the

Read the thread · 2026-05-29 · closed · 1 comment

concentration_analyze: Usage Guidelines 3/5 → 5/5

Tool: concentration_analyze (functions/_lib/mcp-tools.ts:207) Dimension: Usage Guidelines Current score: 3/5 Target: 5/5

Glama TDQS feedback (verbatim)

The description explains when to use the tool (for concentrated single-stock risk analysis) and provides critical rules about not inventing required fields, but it does not explicitly state when not to use it or suggest alternatives among siblings.

Fix plan

Add a 'When NOT to use' clause: for standalone hedge prici

Read the thread · 2026-05-29 · closed · 1 comment

concentration_analyze: Parameters 4/5 → 5/5

Tool: concentration_analyze (functions/_lib/mcp-tools.ts:207) Dimension: Parameters Current score: 4/5 Target: 5/5

Glama TDQS feedback (verbatim)

The description explains key parameters like totalAssets and ticker in detail, clarifying that totalAssets must be user-supplied and ticker can substitute expected returns. With only 29% schema coverage, this adds meaningful semantic value.

Fix plan

Backfill description: on the remaining undescribed properties: positio

Read the thread · 2026-05-29 · closed · 1 comment

concentration_analyze: Completeness 4/5 → 5/5

Tool: concentration_analyze (functions/_lib/mcp-tools.ts:207) Dimension: Completeness Current score: 4/5 Target: 5/5

Glama TDQS feedback (verbatim)

Given the tool's complexity (14 parameters, nested objects, no output schema), the description covers purpose, key parameters, tax components, and the critical user-supplied data rule. A brief mention of the output structure would improve completeness.

Fix plan

Add a 'Returns' block listing top-level keys: `concentrati

Read the thread · 2026-05-29 · closed · 1 comment

concentration_analyze: Conciseness 4/5 → 5/5

Tool: concentration_analyze (functions/_lib/mcp-tools.ts:207) Dimension: Conciseness Current score: 4/5 Target: 5/5

Glama TDQS feedback (verbatim)

The description is well-structured, starting with purpose, then details, then important usage notes. It is somewhat long but every sentence adds necessary information.

Fix plan

Tighten without information loss. Merge the 'three after-tax strategies' clause with the strategy list; collapse the totalAssets caveat into a s

Read the thread · 2026-05-29 · closed · 1 comment

rsu_sell_vs_hold: Usage Guidelines 4/5 → 5/5

Tool: rsu_sell_vs_hold (functions/_lib/mcp-tools.ts:171) Dimension: Usage Guidelines Current score: 4/5 Target: 5/5

Glama TDQS feedback (verbatim)

Includes explicit instructions that required fields must come from user or be derivable from ticker, and warns not to invent values. However, it does not explicitly compare with siblings or state when not to use the tool.

Fix plan

Add 'When to use vs. siblings': for RSU at vest; for ISO/AMT, use amt_iso_optimize; for NS

Read the thread · 2026-05-29 · closed · 1 comment

Most recent

Glama TDQS: equity_funding_plan Parameters dropped to 3 (redundant output-shape prose)

Glama TDQS Parameters for equity_funding_plan stepped 4->3 on 2026-06-13, persistent. The description duplicates the outputSchema (#78) shape prose ('Each NamedPlan carries ...'). Trim the redundant output-shape sentence (keeping the behaviorally-useful four-plan gloss) to reduce bloat. Target: Parameters >=4, no other dimension <4.

Read the thread · 2026-06-18 · closed · 0 comments

Glama TDQS: amt_iso_optimize Parameters dipping to 3 (description bloat / output listing duplicated by outputSchema)

Glama TDQS Parameters for amt_iso_optimize held at 3 from 2026-06-13 (ticked to 4 on 06-18); borderline. The description re-lists all output keys in prose, now duplicated by the outputSchema from #78, bloating the tool definition. Trim the output-key prose to a one-liner pointing at outputSchema to reduce bloat and let the input-param docs read clearly. Target: Parameters solidly >=4, no other dimension <4.

Read the thread · 2026-06-18 · closed · 0 comments

rsu_sell_vs_hold: Parameters 3/5 → 5/5

Tool: rsu_sell_vs_hold (functions/_lib/mcp-tools.ts:171) Dimension: Parameters Current score: 3/5 Target: 5/5

Glama TDQS feedback (verbatim)

With only 27% schema description coverage, the description adds meaning for ticker and expectedSalePrice but fails to explain key parameters like ordinaryIncome, filingStatus, stateCode, and haircut. Partial compensation.

Fix plan

Add description: to every rsu_sell_vs_hold inputSchema property. 8 properties currently undesc

Read the thread · 2026-05-29 · closed · 1 comment

rsu_sell_vs_hold: Completeness 4/5 → 5/5

Tool: rsu_sell_vs_hold (functions/_lib/mcp-tools.ts:171) Dimension: Completeness Current score: 4/5 Target: 5/5

Glama TDQS feedback (verbatim)

Covers algorithm, assumptions, and required data rules. Lacks output format description, but given complexity and no output schema, it is reasonably complete.

Fix plan

Add a 'Returns' block listing computeRsuResult's top-level keys: vest (tax breakdown at vest), hold (LTCG outcome at end of holdYears), sellNowInvest (

Read the thread · 2026-05-29 · closed · 1 comment

qsbs_check: Usage Guidelines 4/5 → 5/5

Tool: qsbs_check (functions/_lib/mcp-tools.ts:284) Dimension: Usage Guidelines Current score: 4/5 Target: 5/5

Glama TDQS feedback (verbatim)

The description emphasizes that all required fields must come from the user and instructs the model not to invent values. It also explains how to handle 'unsure' enums. However, it does not explicitly state when to use this tool over alternatives, though siblings are unrelated.

Fix plan

Add a sentence stating this tool is for

Read the thread · 2026-05-29 · closed · 1 comment

qsbs_check: Parameters 3/5 → 5/5

Tool: qsbs_check (functions/_lib/mcp-tools.ts:284) Dimension: Parameters Current score: 3/5 Target: 5/5

Glama TDQS feedback (verbatim)

Schema description coverage is 0%, so the description must compensate. It provides high-level context by listing the eight tests and grouping parameters, but does not explain each parameter individually. Parameter names are somewhat self-explanatory, and the description mentions the 'unsure' fallback for enums, but deeper meaning is lac

Read the thread · 2026-05-29 · closed · 1 comment

qsbs_check: Completeness 4/5 → 5/5

Tool: qsbs_check (functions/_lib/mcp-tools.ts:284) Dimension: Completeness Current score: 4/5 Target: 5/5

Glama TDQS feedback (verbatim)

Given 12 required parameters and no output schema, the description explains return values (verdict, exclusion %, tax saved, state conformity) and includes important usage constraints. It is sufficiently complete for an agent to invoke correctly, though more detail on output format could help.

Fix plan

Add a 'Returns' block listin

Read the thread · 2026-05-29 · closed · 1 comment

qsbs_check: Behavior 4/5 → 5/5

Tool: qsbs_check (functions/_lib/mcp-tools.ts:284) Dimension: Behavior Current score: 4/5 Target: 5/5

Glama TDQS feedback (verbatim)

Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, which are consistent with a non-destructive 'check'. The description adds value by detailing the output (verdict, exclusion percentage, tax saved, state conformity) and the constraint on required fields, without contradicting annotations.

Fix plan

Add

Read the thread · 2026-05-29 · closed · 1 comment

The remaining reports are on the project's issue tracker.