Skip to main content
Glama

net_worth_tracker__net_worth

Calculate net worth by subtracting liabilities from assets. Input your financial data to assess your financial health.

Instructions

[net-worth-tracker] net_worth

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetsYes
liabilitiesYes
Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It fails to state whether the tool performs a calculation, mutates data, or requires specific prerequisites. The word 'net_worth' implies computation, but the description does not confirm this or describe any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

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

The description is a single phrase that provides no actionable information. This is under-specification, not conciseness. Every sentence should earn its place; here, no sentence provides value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of two required object parameters, no schema descriptions, no output schema, and several sibling tools in the same domain, the description is completely inadequate. An agent has no basis to correctly invoke or interpret the tool's behavior.

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

Parameters1/5

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

The schema has 0% description coverage for parameters, and the tool description adds no meaning. The parameters 'assets' and 'liabilities' are typed as objects with no further indication of expected structure, keys, or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '[net-worth-tracker] net_worth' is a tautology, restating the tool name without indicating the tool's function. It does not specify that the tool calculates net worth as assets minus liabilities, nor does it distinguish it from sibling tools.

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

Usage Guidelines1/5

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

No usage guidelines are provided. The description lacks any indication of when to use this tool instead of alternatives such as 'asset_allocation' or 'debt_to_asset_ratio', leaving the agent without context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GAJETOso/financeskills'

If you have feedback or need assistance with the MCP directory API, please join our Discord server