get_prices
Current price per ticker with its source, quote currency and recent change, plus any manual overrides.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Krosos
by com.krosos
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are given, so the description is the sole source. It indicates a read-only operation (get) and outlines the data returned, but does not mention permissions, rate limits, or any side effects. As a getter, this is largely transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that conveys all key aspects of the tool without unnecessary detail. It is concise and to the point.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of an output schema, the description adequately lists the data fields (source, quote currency, recent change, manual overrides). It does not specify the exact output format (e.g., list vs. dictionary), but this is a minor omission.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has no parameters, so no parameter explanation is needed. The description appropriately focuses on the output, making this dimension trivially satisfied.
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?
The description clearly states the tool returns current price per ticker, including source, quote currency, recent change, and manual overrides. This is specific and distinguishes it from other data-retrieval tools like get_dashboard or get_net_worth.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for retrieving price data but does not explicitly state when to prefer this over sibling tools. No guidance on context or alternatives is provided, though the purpose is clear from the name and description.
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.
TDQS
A4/5.0
Disambiguation5/5
Each tool targets a distinct domain operation: dashboard views, history, pricing, projections, reference data, tax reports, connections, transactions, trade logging, balance adjustments, and syncing. There is no overlap between read-only queries and mutation commands, so an agent should be able to select the right tool for a specific task without confusion.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern: get_dashboard, get_net_worth_history, get_prices, get_projection_config, get_reference_data, get_tax_report, list_connections, list_transactions, log_trade, record_balance_adjustment, refresh_prices, sync_connections. The verbs (get, list, log, record, refresh, sync) are clear and align with the noun they operate on.
Tool Count5/5
Twelve tools is well-scoped for a personal finance/ledger server. Each tool covers a necessary aspect of the domain (viewing, reporting, data entry, sync), and none feel redundant or excessive. This fits the typical range for a coherent service.
Completeness4/5
The surface covers core read operations (dashboard, history, prices, reference data, tax, transactions), mutation operations (log_trade, record_balance_adjustment), and maintenance operations (refresh_prices, sync_connections). Missing could be an update/delete for transactions or connections, but the provided tools cover the primary lifecycle of a financial ledger without dead ends.