Skip to main content
Glama

Unit Learning Curve Time

bpj_wright_unit_learning_time
Read-onlyIdempotent

Use a unit-time learning curve in which each doubling of cumulative output multiplies the individual unit time by a fixed fraction.

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": {
      "first": "<first>",
      "learning": "<learning>",
      "unit": "<unit>"
    },
    "name": "bpj_wright_unit_learning_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
firstYes
learningYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds the core calculation behavior—unit time changes by a fixed fraction at each doubling of cumulative output—but omits the exact formula, output form, and assumptions, so it adds useful but incomplete behavioral context.

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?

It is a single dense sentence with no filler, and the model constraint is front-loaded. The terseness contributes to missing detail, but from a conciseness/structure standpoint it is efficient.

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?

For a three-parameter calculation tool with no output schema and no parameter descriptions, the definition is too thin: it does not state what value is returned, the exact curve formula, or how to interpret the inputs. The annotations cover safety but not calculation semantics.

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

Parameters2/5

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

Schema description coverage is 0%, so the description should explain the three required inputs; however, it only alludes to 'cumulative output', 'individual unit time', and 'fixed fraction'. It never maps those concepts to first, unit, or learning explicitly, leaving parameter meaning to schema titles.

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

Purpose3/5

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

The description names the model ('unit-time learning curve') and the doubling relationship, but the verb is 'Use' rather than a precise action like 'compute', and it never states the returned quantity or distinguishes this tool from any sibling. An agent can infer the domain but not the exact operation with confidence.

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

Usage Guidelines2/5

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

There is no when-to-use/when-not guidance, no prerequisites, and no named alternative among the many sibling tools. At best the model name implies the learning-curve use case; otherwise the agent must infer applicability.

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.