{
  "id": 21213739,
  "title": "Three Candidates for One Tool Slot — Pricing Our MCP Server's Third Tool",
  "url": "https://urgent.news/2026/11/22/three-candidates-for-one-tool-slot-pricing-our-mcp-servers-third-tool",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-22T13:10:32.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/eliashivemind/three-candidates-for-one-tool-slot-pricing-our-mcp-servers-third-tool-15jf"
  },
  "original_language": "en",
  "account": "Three candidates have been proposed for the third tool slot on our MCP server, and their performance has been evaluated. Candidate 1, nim_get_job_status, is the strongest candidate on value, as it would allow for asynchronous generation and avoid blocking, guessing, or re-firing jobs. However, adding this tool would increase the server's total schema to 1,028 chars and ~257 tokens per turn, which is close to the budget limit. Candidate 2, nim_upscale_image, would add 302 chars and ~76 tokens per turn, but the trap is that there is currently no workflow waiting on an upscale. This tool is cheap but not earned, and its addition could lead to a 50-tool server at ~100 tokens per head. Candidate 3, nim_create_media, is the most feature-rich option but also the most expensive, costing 1,449 chars and ~363 tokens per turn. This tool attempts to replace multiple tools with a single flexible tool, but the measured cost is higher than the combined cost of the existing tools. The decision rule was based on real workflow needs, cost, and the potential for future candidates. The server will remain at two tools, with Candidate 1 ready to be added when the server goes asynchronous.",
  "summary": "Three Candidates for One Tool Slot — Pricing Our MCP Server's Third Tool A few days ago I published the audit of our MCP server, nova-ops-nim-mcp : two tools, 790 serialized characters, roughly 198 estimated tokens re-sent on every turn — and the rule we adopted before growing it. Measure every candidate, keep the server's total schema under 1,000 estimated tokens per turn, and keep property…",
  "key_points": [
    "Candidate 1, nimgetjobstatus, strongest on value but increases schema to 1,028 chars",
    "Candidate 2, nimupscaleimage, cheapest option but no current workflow need",
    "Candidate 3, nimcreatemedia, most feature-rich but most expensive at 1,449 chars"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}