Skip to main content
Glama
Dairus01

Interswitch MCP Server

by Dairus01

isw_request_nano_loan

Request a nano loan. Provide customer ID and loan amount in Naira or Kobo. Confirmation is required for this high-risk operation.

Instructions

Request a nano loan. High-risk operation creating debt; requires confirm: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
extraNo
tenorNo
confirmNoRequired as true for write or high-risk tools.
amountKoboNoAmount in kobo. Do not combine with amountNaira.
customerIdYes
amountNairaNoAmount in Nigerian Naira. Do not combine with amountKobo.
merchantCodeNo
transactionRefNo
Behavior3/5

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

With no annotations, the description highlights high-risk and debt creation, but lacks details on idempotency, authorization needs, or rate limits. The confirm requirement is noted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise with two sentences that front-load the action and risk, every word earns its place.

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

Completeness2/5

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

For a high-risk operation with 8 parameters and no output schema, the description lacks prerequisites, error handling, and return value information, making it incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 38% and the description adds no parameter-level information, failing to explain critical fields like customerId, tenor, or merchantCode.

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 clearly states the tool requests a nano loan and identifies it as high-risk, but does not distinguish it from sibling lending tools like isw_salary_lending or isw_value_financing.

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?

The description mentions the confirm parameter requirement but provides no guidance on when to use this tool versus other loan tools or any prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Dairus01/Interswitch-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server