Skip to main content
Glama

Quanta Finance Deal Check

List loan programs

list_loan_programs
Read-onlyIdempotent

List Quanta Finance loan programs (name, slug, summary, tagline, url). A slug returns one program with its page FAQ. Each result starts with a notice that it is an estimate, and carries the next step and the disclaimer.

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

Input Schema

NameRequiredDescriptionDefault
slugNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: every result is prefixed with an estimate notice and carries a next step and disclaimer, and a slug lookup also returns page FAQ content. No output schema exists, so this return-shape information is valuable and appropriately placed.

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?

Three short sentences, front-loaded with the tool's identity and returned fields, then the slug behavior, then the per-result contents. Dense but no filler; every sentence contributes.

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?

For a one-optional-param read-only list tool with no output schema, the description covers identity, filtering behavior, and the shape of returned results. Nothing an agent needs in order to call it correctly appears to be missing.

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 0% and the single parameter's enum values are only in the schema, so the description must carry meaning for slug. It does: passing a slug returns exactly one program plus that program's page FAQ, which is more than the schema's bare enum conveys. It stops short of explaining what the individual slugs mean, though those are largely self-describing.

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?

States a specific verb and resource ('List Quanta Finance loan programs') and enumerates the fields returned (name, slug, summary, tagline, url). It doesn't differentiate itself from the sibling check_deal_fit, but the scope of the tool is unambiguous on its own.

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 sentence 'A slug returns one program with its page FAQ' tells the agent that omitting slug lists all programs and supplying it narrows to one. There is no explicit when-to-use or when-to-prefer-check_deal_fit guidance.

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