Skip to main content
Glama

SMIFS Limited

Product details and FAQs

get_product
Read-onlyIdempotent

Details for one SMIFS product line or offering, by slug from list_products. A product line (for example "wealth-management") returns its summary, page URL, offerings and the FAQs shown on its page; an offering (for example "pms-and-advisory") returns its summary, page URL and the product line it belongs to.

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": {
      "slug": "<slug>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesProduct or offering slug from list_products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the disclosure of what each variant returns — summary, page URL, offerings, FAQs for a line; summary, page URL and parent line for an offering. That is real behavioral context beyond the annotations. It does not mention error behavior for an unknown slug, which keeps it from a 5.

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 front-loaded sentence that names the resource first, then the two behavioral cases in order. It is dense rather than padded, though the parenthetical examples and 'the FAQs shown on its page' add a little length that could be tightened.

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?

With no output schema, the description carries the burden of describing returns and does so for both variants, plus the slug provenance. Only the failure mode for an invalid or unmatched slug is left unstated.

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 100%, so the baseline is 3; the description earns above that by explaining that the single slug parameter is polymorphic — it can identify either a product line or an offering, and the two produce different result sets. That distinction is not expressible in the schema's maxLength/minLength constraints.

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?

States a specific verb and resource ('Details for one SMIFS product line or offering') and immediately distinguishes the two entity shapes it can return. Naming the slug source as list_products separates it cleanly from that sibling without needing the schema.

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

Usage Guidelines4/5

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

Explicitly tells the agent to obtain the slug from list_products, which is the key prerequisite. It also implies when each return shape applies (product line vs offering), but gives no explicit exclusion or fallback for a slug that matches neither.

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