Skip to main content
Glama
MITDEVPRO

finanzas-mcp

by MITDEVPRO

working_capital

Read-onlyIdempotent

Calculate working capital and operational fund needs (NOF) using accounts receivable, inventory, and accounts payable.

Instructions

Capital de trabajo contable y necesidad operativa de fondos (NOF = CxC + inventario - CxP).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cxcYesCuentas por cobrar
cxpYesCuentas por pagar
inventarioYesInventario
ventas_anualesNoVentas anuales para expresar la necesidad como % (0 = omitir)
activo_corrienteNoActivo corriente total (0 = usar solo componentes operativos)
pasivo_corrienteNoPasivo corriente total (0 = usar solo componentes operativos)
Behavior4/5

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds the computation logic (the formula for NOF), which provides transparency beyond annotations about what the tool actually computes.

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?

A single, clear sentence that efficiently states the purpose and the formula. No wasted words; every part is necessary.

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

Completeness3/5

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

The description defines the tool's output (working capital and NOF) but does not explicitly state the return format. With no output schema, the description could hint at whether the result is a single number or both values. It is adequate but could be more explicit.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for all parameters. The description names the three required parameters in the formula but does not add meaning beyond the schema's own descriptions. Baseline 3 is appropriate.

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 calculates accounting working capital and operating funds need (NOF), including the formula. It uses specific financial terms and implicitly distinguishes from sibling financial tools like ratios or DCF.

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 provides the formula and context (working capital and NOF), but does not explicitly mention when to use this tool versus alternatives like other financial calculations. Usage is implied by the formula, but no exclusion or alternative guidance is given.

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/MITDEVPRO/finanzas-mcp'

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