Skip to main content
Glama

Get a loan

get_loan
Read-onlyIdempotent

Status, collateral, buyback cost and remaining amount, due date and lenders for one loan.

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": {
      "loan_id": "<loan_id>"
    },
    "name": "get_loan"
  }
}

Input Schema

NameRequiredDescriptionDefault
loan_idYesLoan ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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, so the safety profile is covered. The description adds real value by disclosing the returned attributes (collateral, buyback cost, remaining amount), but says nothing about behavior for an unknown loan_id or whether the read reflects live chain state.

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?

A single compact clause with zero filler, front-loaded with the most relevant returned fields. It is a noun phrase rather than a sentence, so the operation itself must be inferred, which costs it a point.

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

Completeness3/5

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

For a one-parameter read tool with no output schema, listing the returned fields is the right compensation and largely covers the shape of the response. Gaps remain around missing-loan handling and how this differs from the sibling loan-listing tool.

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 description coverage is 100% and the single parameter loan_id is documented, so the schema carries the parameter burden. The description only reinforces that the ID selects exactly one loan; it adds no format, source, or validity detail beyond 'Loan ID'.

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 enumerates exactly what is retrieved — status, collateral, buyback cost, remaining amount, due date and lenders — for a single loan, which tells an agent precisely what data comes back. It lacks an explicit verb and never names the sibling it contrasts with, so the single-vs-multiple distinction from get_borrower_loans is only implied by 'one loan'.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no prerequisites, and no named alternative. An agent must infer from the phrase 'for one loan' that this is the single-loan drill-down rather than the portfolio listing in get_borrower_loans.

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.