Skip to main content
Glama

Price an AI feature

price_ai_feature
Read-onlyIdempotent

Work out an AI feature's unit economics and pricing: cost per request and per user (light, typical, heavy), levers like caching and routing, pricing options with margins, guardrails, and the assumptions to validate. Returns instructions to follow with the user's text.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
featureNoWhat the feature does, the model it uses, expected usage, and how the product is priced today

Output Schema

NameRequiredDescriptionDefault
textYesThe answer in markdown, as shown to the user; for the guides, instructions to follow with the user's text
linksYesThe AI PM Lab pages the answer links to, where each idea can be tried hands-on

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "links": {
      +      "description": "The AI PM Lab pages the answer links to, where each idea can be tried hands-on",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "text": {
      +      "description": "The answer in markdown, as shown to the user; for the guides, instructions to follow with the user's text",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "text",
      +    "links"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the tool does not compute a result itself but 'returns instructions to follow with the user's text,' which tells the agent the response is procedural guidance to act on, not a finished answer.

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?

One front-loaded sentence delivers the purpose and then the deliverable list, with a second short sentence for the return behavior. No filler, no repetition of the title, and the most decision-relevant information (scope, then what comes back) is ordered first.

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?

With an output schema present, return values needn't be detailed, and the description still flags that the return is instructions rather than numbers. For a one-parameter, read-only advisory tool this is nearly complete; the only gap is routing guidance against the cost/compare siblings.

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?

There is a single optional parameter and schema description coverage is 100%, with the schema already specifying what to include ('what the feature does, the model it uses, expected usage, and how the product is priced today'). The description's mention of 'the assumptions to validate' lightly reinforces that free-text input matters, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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-and-resource pair ('work out an AI feature's unit economics and pricing') and enumerates the concrete outputs: cost per request, per-user tiers, caching/routing levers, pricing options with margins, guardrails. That is far more specific than a sibling like estimate_cost, though it never explicitly contrasts itself with that sibling.

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?

Usage is only implied by the enumerated scope — an agent can infer this is the broad 'price my feature end to end' tool rather than a narrow cost lookup. There is no explicit when-to-use statement and no mention of when to prefer estimate_cost or compare_models instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources