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

ohneben's Wafeq MCP

by ohneben
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

wafeq_quotes_retrieve

Read-onlyIdempotent

Get a specific quote's details by providing its ID. Use this read-only tool to fetch a single quote from Wafeq for review or further processing.

Instructions

🟢 READ-ONLY · Quotes · GET /quotes/{id}/

Retrieve quote

Endpoint for retrieving a single quote.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the READ-ONLY prefix adds no new behavioral information. The description does not disclose response shape, error behavior, authentication needs, or other side effects beyond what annotations cover.

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

Conciseness3/5

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

The route and resource line is front-loaded and compact, but 'Retrieve quote' and 'Endpoint for retrieving a single quote' are redundant restatements of the same action. The description is short but contains repeat filler instead of earning each sentence.

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 simple one-parameter read-only endpoint, the route and single-quote wording give enough context, and the annotations fully cover the safety profile. The lack of explicit output or error details is a minor gap for an operation whose return value is self-evident.

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?

With 0% schema description coverage, the description compensates by showing the id in the route template GET /quotes/{id}/, so the agent knows the parameter is a path variable. For a single self-evident id parameter, this is sufficient semantic guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Retrieve quote' and 'Endpoint for retrieving a single quote.' Including the explicit route GET /quotes/{id}/ and the word 'single' distinguishes it from wafeq_quotes_list, create, update, and destroy siblings.

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: 'retrieving a single quote' suggests use when an ID is known. The description names no alternatives and gives no explicit when-not-to-use guidance versus other quote-related endpoints.

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