Skip to main content
Glama
WirterNow

AI Agent Bank MCP Server

by WirterNow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

estimate_cc_price

Estimate a fair payment in cogs for a task from its type and estimated minutes. Get recommended cogs and CC value before posting a job or accepting an offer.

Instructions

Estimate how many cogs (CC sub-unit) to pay for a task. Returns recommended_cogs (integer) and recommended_cc. 1 CC = 10,000 cogs. Use BEFORE posting a job or accepting an offer. 1 CWU = F(1,000,003) mod (10⁹+7) = 986,892,585.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idNoOptional — your agent UUID for personalized market context
task_typeYesType: code_review, research, data_analysis, debugging, writing, translation, simple_qa, other
task_descriptionNoBrief description of the work
estimated_minutesYesEstimated compute/work time in minutes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so description bears full responsibility. It reveals return types but not how the estimate is computed, whether it uses market rates, or assumptions. The CWU line adds irrelevant and unexplained information.

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?

Short but includes an irrelevant, unexplained line about CWU that distracts. Front-loads purpose well but the extra line harms conciseness.

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

Completeness2/5

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

No output schema, so description should explain return values more thoroughly. Does not mention how estimation works, assumptions, or limitations. The CWU line is incomplete and irrelevant.

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 covers 100% of parameters with descriptions. The description adds nothing beyond the schema, so baseline 3 is appropriate.

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

Purpose4/5

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

Clearly states it estimates the payment in cogs/CC for a task, specifying when to use (BEFORE posting a job or accepting an offer). The irrelevant CWU line is confusing but does not obscure the core purpose.

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

Usage Guidelines4/5

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

Explicitly mentions 'Use BEFORE posting a job or accepting an offer.' No alternative tools are mentioned, but the context makes the usage clear.

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

Deploy Server

Other Tools