Skip to main content
Glama
Sign In

fermi

by io.github.Kromatic-Innovation
OverviewDiscussionsAdmin

List your past estimates (account only)

list_my_estimates
Read-onlyIdempotent

Lists the past estimates on your account, newest first. Use this when the user wants to find an earlier estimate ("what did I estimate last week?") or has lost an estimate_id.

Returns estimates, each with estimate_id, created_at, question, unit, target_horizon, point_estimate, estimation_interval, distribution_family and status; and next_offset, the offset of the next page, or null on the last page. For an estimate's full detail, pass its estimate_id to get_estimate_result.

Estimates made without an account cannot be listed. To get an account, call POST https://fermi.kromatic.com/api/v1/accounts (it returns an api_key once; a new account starts with 3 credits), or sign in through your connector. If you cannot make HTTP requests, ask the user to do one of these.

Cost: free, but account only: without an account the call is refused with a sign-in requirement.

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_my_estimates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many estimates to return, 1 to 100. Default 20.
offsetNoHow many of the newest estimates to skip, for paging: pass the previous page's next_offset. Default 0.
api_keyNoYour Fermi API key. Required unless your connector is signed in. Get one with POST https://fermi.kromatic.com/api/v1/accounts.

Output Schema

NameRequiredDescriptionDefault
billingNoWho this call was billed to and what is left. Present on every Fermi result.
estimatesNoYour estimates, newest first.
next_offsetNoPass as offset for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description wisely spends its space on what annotations cannot convey: newest-first ordering, the next_offset paging contract, and the exact failure mode (refused with a sign-in requirement). The auth remediation path and cost model are spelled out in enough detail to recover from an error without guessing.

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 purpose and use case before the account prerequisites, and the four paragraphs map to distinct concerns. Minor redundancy in covering cost/account twice ('3 credits' and 'Cost: free, but account only'), which costs a little tightness.

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

Completeness5/5

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

Everything an agent needs to call this correctly is present: when to use it, paging, the auth prerequisite with a concrete remedy, and the sibling to call for detail. The enumerated return fields are arguably redundant given the output schema, but they are harmless and confirm the shape.

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?

Schema coverage is 100%, so the baseline is 3; the description goes slightly beyond by describing the paging loop concretely ('next_offset, the offset of the next page, or null on the last page') and restating the api_key requirement in prose. It doesn't add format or edge-case detail for limit beyond what the schema already says.

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 and resource with scope and ordering: 'Lists the past estimates on your account, newest first.' It also implicitly distinguishes itself from get_estimate_result by routing to that tool for full detail, so an agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

Gives concrete triggering situations ('what did I estimate last week?', 'has lost an estimate_id') and names the alternative: pass estimate_id to get_estimate_result for full detail. It also states the exclusionary condition — estimates made without an account cannot be listed.

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

All fermi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources