Skip to main content
Glama

Equitest

Get a financial model template

get_financial_model
Read-onlyIdempotent

Returns one industry financial model template, chosen by id or name: its 13 sheets and what each contains, the export formats and languages, what opening it costs this user (and whether it is free because the user opened it in the last 30 days), and the link that opens it in Equitest. The model itself is built and edited in Equitest, starting from the Assumptions sheet.

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": {
      "model": "<model>"
    },
    "name": "get_financial_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesTemplate id or name, e.g. "restaurant", "SaaS", "Law Firm"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 bar is lower. The description nonetheless adds real behavioral context beyond them: that the result includes the cost of opening for this user and whether it is currently free due to a 30-day access window, plus an Equitest deep link — details an agent could not get 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?

The return payload is front-loaded in the first sentence, followed by a short scoping note about where editing happens. The middle clause is a dense run-on enumeration of return fields, but no sentence is filler.

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?

There is no output schema, so the description must carry the return shape — and it does, covering sheet count and contents, export formats, languages, per-user cost/free-window status, and the opening link. For a single-parameter read tool this is sufficient to call it correctly.

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?

Schema coverage is 100% for the single 'model' parameter, and the schema itself already documents id-or-name with examples ('restaurant', 'SaaS', 'Law Firm'). The description repeats 'chosen by id or name' without adding resolution rules such as ambiguity handling for duplicate names, so baseline 3 applies.

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 — 'Returns one industry financial model template' — plus the selection mechanism (id or name). The singular 'one ... template' implicitly separates it from list_financial_models without needing to name the 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: the reader infers this is the tool for fetching a single template's details and opening link, while listing all templates belongs elsewhere. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must reason from the singular/plural contrast.

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