character-forge-mcp

Overview Schema Source Related Servers Discussions Admin

What a character has cost

character_costs

Read-only

Calculates total estimated USD costs for a character's paid generations, itemizing concept, scene, video, music, and voice pricing.

Instructions

Free. Shows the character's paid generations (concept, scene, video, music, voice) with estimated USD from models.json pricing, and the total.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "character_costs"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real value beyond that: the call itself is free, prices are 'estimated' and derived from models.json (so they are config-driven approximations, not billed amounts), and only 'paid' generations are included, excluding free ones — all non-obvious traits.

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

Conciseness4/5

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

A single well-packed sentence with the most actionable attribute ('Free') front-loaded, followed by the return contents and the pricing source. The parenthetical category list is informative rather than padding, though the sentence is dense.

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?

For a one-parameter read-only tool with no output schema, the description covers what is returned (per-category breakdown plus total), how figures are computed (models.json estimates), and the free-to-call nature. Only the meaning/format of the id argument remains under-specified.

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 description coverage is 0% for the single required parameter 'id', so the description must compensate. The phrase 'the character's' weakly implies id is a character identifier, but it never states the format or which character-id namespace applies, leaving the parameter only partially clarified.

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?

The description names a specific verb ('Shows') and a specific resource ('the character's paid generations') and enumerates the categories covered (concept, scene, video, music, voice) plus the total. This clearly separates it from generic siblings like character_get or character_list, which do not report cost breakdowns.

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?

'Free' signals that this is a no-charge lookup and the cost focus implies usage when budgeting or auditing spend, but no alternative is named and no explicit when-not condition is given. An agent must infer that this is the cost-inspection counterpart to character_get.

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