Skip to main content
Glama

Headroom Desk options calculators

Annualized return

annualized_return
Read-onlyIdempotent

Turns a return over a number of calendar days into per-year figures, simple and compounded, shown beside the period return.

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": {
      "return_pct": "<return_pct>",
      "days": "<days>"
    },
    "name": "annualized_return"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
return_pctYesReturn over the period in percent; a loss with a minus, not below -100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, closed-world calculation with no destructive effects. The description adds useful behavioral context by saying the result includes simple and compounded annualized figures shown beside the period return, which is important because no output schema exists. It does not disclose day-count conventions, rounding, or handling of edge cases such as very short periods.

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?

The definition is a single efficient sentence that front-loads the core transformation and then names the outputs. There is no filler or redundancy. It could be slightly more informative without becoming verbose, but its current structure is clean.

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

Completeness3/5

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

For a two-parameter calculator with annotations covering safety and no output schema, the description does enough to explain the calculation result. However, it leaves the days parameter semantically underspecified and provides no usage guidance relative to sibling tools. Completeness is adequate but not thorough.

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 coverage is only 50%: return_pct is described in the schema, but days has only a type and minimum with no semantic explanation. The description mentions calendar days but does not explicitly connect that to the days parameter, explain how partial years are treated, or clarify whether days means holding period, elapsed calendar days, or trading days. It therefore does not compensate for the schema gap.

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 states a specific transformation: converting a period return over calendar days into annualized returns. It clearly names the outputs (simple and compounded, alongside the period return), so an agent can tell what the tool computes. It does not explicitly differentiate itself from the sibling option-pricing tools, but the purpose is otherwise unambiguous.

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?

The description explains what the tool does but gives no guidance on when to use it or when to prefer an alternative. There is no mention of prerequisites, input constraints beyond the schema, or suitable contexts such as comparing investments with different holding periods. Usage must be inferred entirely from the purpose sentence.

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