Skip to main content
Glama
Sign In

Widely

by com.widely-mobile
OverviewDiscussionsAdmin

Look up product prices

lookup_pricing
Read-onlyIdempotent

Returns the monthly price with and without VAT, setup fees, and usage rates for a plan, WhatsApp AI, the AI receptionist, a phone number, data, calls, or a port. Filter by product, country, or number type. No sign-in. not_priced means that price engine has no amount. This does not charge.

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": "lookup_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoISO-2 or country name. IL selects ILS.
productNopro, business, free, whatsapp_ai, ai_receptionist, phone_number, travel_data, calls, sms, number_port, or a channel pack. Omit to use question, or to list the catalog.
currencyNoGBP, EUR, USD, or ILS. Defaults from the country, else EUR.
questionNoThe price question, when it names more than one product.
number_typeNomobile, geographic, national, or toll_free. Omit to keep the number matrix.
includes_origin_callsNoOmit when the caller did not say whether calls to that country are included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, yet the description still adds real value: 'No sign-in' discloses the auth requirement, 'not_priced means that price engine has no amount' explains a sentinel return value in the absence of an output schema, and 'This does not charge' rules out any billing side effect. Minor gap: nothing about currency fallback or response granularity beyond the field list.

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?

Four short sentences, front-loaded with the return payload before filtering and behavioral caveats. The clipped phrasing ('No sign-in.') is efficient rather than confusing, though the fragmented style slightly reduces smoothness.

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 six all-optional parameters, full schema coverage, and no output schema, the description carries the return-value burden and does so by listing price components and the not_priced sentinel. The remaining shortfall is routing clarity against the many quote_* and rate-lookup siblings.

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 100%, so the schema already explains each of the six parameters, and the baseline is 3. The description reinforces which dimensions can be filtered on (product, country, number type) and names the product family, but adds little syntax or default behavior beyond what the schema says.

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 states a concrete verb and resource ('Returns the monthly price... setup fees, and usage rates') and enumerates the covered products (plan, WhatsApp AI, AI receptionist, phone number, data, calls, port), so an agent knows exactly what it retrieves. It does not, however, distinguish itself from near-neighbors like quote_call, quote_number, get_data_rate, or explain_charges, leaving overlap unresolved.

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?

'Filter by product, country, or number type' and 'This does not charge' imply this is the non-binding informational lookup, which is useful context. But there is no explicit when-to-use/when-not guidance and no named alternative such as quote_call or get_did_rate for the more specific quoting cases.

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

All Widely toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources