Skip to main content
Glama

IFC India Import Duty & Landed Cost

Get a confirmed quote from IFC

contact_ifc
Read-onlyIdempotent

Returns how to contact IFC - Imports From China (WhatsApp, calculator, website) for a confirmed China to India shipping and customs clearance quote.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "contact_ifc"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond them by disclosing the return content (contact channels: WhatsApp, calculator, website), which matters since there is no output schema.

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?

A single front-loaded sentence with no filler; the purpose and the payload are stated immediately, and the parenthetical efficiently enumerates the returned channels.

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 zero-parameter, read-only retrieval with rich annotations and no output schema, the description adequately covers what the agent needs: the action, the vendor, and the returned contact methods. Minor gap: it doesn't say whether the returned details are static or refreshed.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies a no-input invocation by describing only a returned result, with no parameter semantics needed or missing.

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?

States a specific verb and resource: 'Returns how to contact IFC - Imports From China'. It also names the concrete channels returned (WhatsApp, calculator, website), so an agent knows exactly what comes back. It doesn't explicitly contrast itself with siblings like estimate_landed_cost, but the purpose is unmistakable.

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?

The phrase 'for a confirmed China to India shipping and customs clearance quote' implies the trigger condition, distinguishing it implicitly from estimate_landed_cost's estimated quote. However, no explicit when-to-use/when-not statement or named alternative is given, so usage must be inferred.

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