VoiceBrief MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_stock_metricA | Answer one financial metric for a US public company, spoken as a single natural-language sentence grounded in that company's most recent SEC 10-K filing (via EDGAR's XBRL data) -- not a guess. Use for a specific spoken question like "what's Tesla's revenue" or "what's Apple's earnings per share". Metric must be one of: revenue, eps, book_value_per_share, market_cap, total_assets, total_liabilities, price. |
| get_stock_snapshotA | Give a short spoken financial snapshot of a US public company (revenue, earnings per share, market cap, book value per share) grounded in its most recent SEC 10-K filing. Use for a broad spoken question like "tell me about Apple's financials" rather than one specific figure. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
get_stock_metric targets a single, specified metric while get_stock_snapshot returns a fixed multi-metric overview, so their primary intents are distinct. There is slight overlap because the snapshot includes several metrics that could also be requested individually, but the descriptions clearly separate specific from broad questions.
Both tools follow the same get_stock_<noun> pattern with clear, parallel names. There is no style mixing or vague verbing between the two.
Two tools is below the typical 3-15 well-scoped range and the server feels minimal, though its narrow voice-brief purpose limits the need for many tools. Each tool earns its place, but the set remains borderline thin.
All advertised metrics are directly queryable via get_stock_metric, and get_stock_snapshot covers the common broad summary. Custom multi-metric requests require repeated calls, but there are no dead ends for the stated domain.