Skip to main content
Glama

net_worth_tracker__debt_to_asset_ratio

Calculate the debt-to-asset ratio by dividing total liabilities by total assets. Assess financial leverage and solvency.

Instructions

[net-worth-tracker] debt_to_asset_ratio

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetsYes
liabilitiesYes
Behavior1/5

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

The description does not disclose any behavioral traits such as whether the tool is read-only, destructive, or requires authentication. No annotations exist to fill this gap.

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

Conciseness2/5

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

While short, the description is under-specified and fails to convey any useful information. True conciseness requires efficient communication, not merely brevity.

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 no output schema, no annotations, and two object parameters with no description, the description is completely inadequate for an agent to correctly invoke the tool.

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 description adds no meaning beyond the schema; both parameters are undocumented objects with no explanation of expected format. Schema description coverage is 0%.

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 is a mere repetition of the tool name with a prefix, providing no indication of the tool's purpose. It is a tautology, similar to the 'Process' calibration example.

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 guidance is provided on when to use this tool versus alternatives, such as other net_worth_tracker tools like net_worth_tracker__asset_allocation.

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