Skip to main content
Glama
Sign In
ohneben's Wafeq MCP

ohneben's Wafeq MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

wafeq_amortizations_retrieve

Read-onlyIdempotent

Retrieve a specific amortization by ID to access its full details. This read-only endpoint lets you fetch a single amortization record for review or verification.

Instructions

🟢 READ-ONLY · Amortizations · GET /amortizations/{id}/

Retrieve amortization

Endpoint for retrieving a single amortization.

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": {
      "id": "<id>"
    },
    "name": "wafeq_amortizations_retrieve"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnly, openWorld, idempotent, and non-destructive behavior. The description adds the GET endpoint and singles out one resource, but provides no additional context such as error responses, auth requirements, or return payload behavior.

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 description is short and front-loaded with the read-only badge and endpoint. The only flaw is redundancy: 'Retrieve amortization' and 'Endpoint for retrieving a single amortization' restate the same idea.

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 retrieve-by-ID tool with rich annotations, the core invocation is clear. However, without an output schema the description does not explain what the response contains, and it gives no context for how to obtain a valid id.

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 0%, so the description must compensate. The path 'GET /amortizations/{id}/' and the phrase 'single amortization' imply that id is the amortization identifier, but the description never explicitly explains id format, source, or validation.

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 uses a clear verb and resource: 'Retrieve amortization' and 'Endpoint for retrieving a single amortization'. It also says 'single', which distinguishes it from wafeq_amortizations_list, though it does not explicitly 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 Guidelines2/5

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

There is no guidance about when to call this instead of related amortization tools. It does not mention that this is the detail-lookup counterpart to the list endpoint, nor does it explain prerequisites such as obtaining an id from the list.

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

Deploy Server

Other Tools