Skip to main content
Glama

Equitest

List financial model templates

list_financial_models
Read-onlyIdempotent

Lists Equitest's 54 industry financial model templates (id and name), the user's access level on the models page and what opening a model costs, and the models the user opened recently. Each model is a live Excel workbook with 13 linked sheets, plus a Word report and a PowerPoint deck from the same numbers, in 11 languages. Optional "search" filters the templates by name.

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

Input Schema

NameRequiredDescriptionDefault
searchNoOptional: part of the industry name, e.g. "restaurant" or "saas"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds useful behavioral context about what the user sees (access level, per-model opening cost, recent models) and what a model actually contains (13 linked sheets, Word/PowerPoint deliverables, 11 languages). It says nothing about ordering, pagination, or result size for a 54-item catalog.

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 core payload — what is listed and what it returns — is front-loaded in the first sentence. The middle sentence about 13 sheets, Word reports, and 11 languages is descriptive marketing detail that does not help an agent invoke the tool and is the main candidate for trimming.

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?

With no output schema, the description carries the burden of describing return values, and it does so concretely (id and name, access level, opening cost, recent models). For a single-optional-parameter list tool that is close to complete, though result ordering and volume remain unstated.

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% and the single 'search' parameter is already documented with an example ('restaurant', 'saas'). The description's 'filters the templates by name' adds only marginal meaning (name-based rather than content-based matching) beyond the schema.

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 opens with a specific verb and resource ('Lists Equitest's 54 industry financial model templates') and enumerates what comes back: ids/names, access level, opening cost, and recently opened models. It is clearly distinct from get_financial_model in intent, but it never names that sibling, so differentiation is left implicit.

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: an agent can infer this is the browse/discovery entry point, and the 'search' sentence hints at narrowing a large catalog. There is no explicit statement of when to call this versus get_financial_model, and no prerequisites or exclusions are given.

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