Skip to main content
Glama

List Hemrock model engines

list_models
Read-only

Lists the hosted Hemrock calculation engines (cap table, exit waterfall, fund economics, and the free unit economics, SaaS forecast and ecommerce forecast models), what each computes, and its price and checkout link. Free and needs no sign-in, so call it when the user asks what Hemrock can calculate or what it costs.

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": "list_models"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful context beyond that: the tool is free, requires no authentication, and each entry includes price and a checkout link — behavior an agent cannot infer from annotations.

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?

Front-loaded with the core action and the enumerated engine list, followed by a short usage sentence. The parenthetical model list is dense but every element earns its place as an inventory of what is returned; only minor tightening is possible.

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?

There is no output schema, but the description compensates by describing what each entry contains (what the engine computes, its price, and a checkout link), plus auth and cost expectations. Nothing critical for a correct call is missing, though a hint about the shape of the returned list would close the remaining gap.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description correctly implies no input is needed by stating it is free and needs no sign-in, which reinforces a no-argument call.

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

Purpose5/5

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

States a specific verb (lists) and resource (hosted Hemrock calculation engines), then enumerates exactly which engines are included (cap table, exit waterfall, fund economics, unit economics, SaaS forecast, ecommerce forecast) and what each record contains. An agent can immediately distinguish this catalog tool from the sibling *_compute tools that do the actual calculations.

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

Usage Guidelines4/5

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

Gives explicit trigger conditions: call when the user asks what Hemrock can calculate or what it costs. It also notes the tool is free and needs no sign-in, removing a usage barrier. It stops short of naming specific alternatives (e.g., 'do not use this to run a calculation, use cap_table_compute'), so routing to compute siblings is left implicit.

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