Skip to main content
Glama
Omnidim

@omnidim-ai/mcp-server

by Omnidim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

purchasePhoneNumber

Destructive

Buys a phone number from the OmniDimension shop, deducts the monthly rental from your wallet, and adds it to your account for attaching to an agent.

Instructions

Buy a phone number from the OmniDimension number shop. The monthly rental comes out of your wallet and the number is added to your account, ready to attach to an agent.

(Tags: Phone numbers)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestBodyYesThe JSON request body.
Idempotency-KeyNoYour own unique key for this purchase, for example a fresh UUID. Strongly recommended: it is what makes a retry safe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.0
    • changedInput schema / properties / requestBody / properties / carrier / description
      Previous value: -"The carrier to buy from: pass the `carrier` the search\nresponse named, so you buy from the inventory you searched.\nAlways required, and omitting it returns\n`409 carrier_required` naming that region's carriers.\n"New value: +"The carrier to buy from: pass the `carrier` the search\nresponse named, so you buy from the inventory you searched.\nRequired where the region has more than one carrier;\nomitting it there returns `409 carrier_required`.\n"
  2. Changed1 schema field changedv0.13.1
    • changedInput schema / properties / requestBody / properties / carrier / description
      Previous value: -"The carrier to buy from: pass the `carrier` the search\nresponse named, so you buy from the inventory you searched.\nAlways required. Region `IN` has `carrier-1` (landline) and\n`carrier-2-new` (mobile); region `US` has `carrier-us`.\nOmitting it returns `409 carrier_required` listing them.\n"New value: +"The carrier to buy from: pass the `carrier` the search\nresponse named, so you buy from the inventory you searched.\nAlways required, and omitting it returns\n`409 carrier_required` naming that region's carriers.\n"
  3. Changed2 schema fields changedv0.13.0
    • addedInput schema / properties / requestBody / properties / carrier
      Added value: +{
+  "description": "The carrier to buy from: pass the `carrier` the search\nresponse named, so you buy from the inventory you searched.\nAlways required. Region `IN` has `carrier-1` (landline) and\n`carrier-2-new` (mobile); region `US` has `carrier-us`.\nOmitting it returns `409 carrier_required` listing them.\n",
+  "type": "string"
+}
    • changedInput schema / properties / requestBody / required
      Previous value: -[
-  "region",
-  "phone_number"
-]New value: +[
+  "region",
+  "carrier",
+  "phone_number"
+]
  4. Addedv0.10.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint/openWorldHint/non-readOnly, so the bar is lower. The description still adds real value by disclosing the business consequence: a recurring monthly rental charged from the wallet and the number becoming attached to the account. It omits retry/idempotency behavior, which is left to the schema.

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?

Two tight sentences front-load the action and then the cost/effect; nothing is redundant. The appended '(Tags: Phone numbers)' is a minor artifact rather than useful prose.

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 usefully covers the outcome (number added, wallet debited) and the follow-on action (attach to an agent). What is missing is the explicit prerequisite of searching first and any note on idempotent retries, though the latter is carried by the schema.

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%; region, carrier (including the 409 carrier_required case) and Idempotency-Key are all documented in the schema. The description adds no further parameter meaning, so the baseline 3 applies.

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 ('Buy') and resource ('a phone number') plus the source ('OmniDimension number shop'), which separates it from importTwilioNumber/importExotelNumber and searchPhoneNumbers. It stops short of explicitly naming those siblings as the ones it is not, so it is clear but not fully differentiated.

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?

'ready to attach to an agent' hints at the sequence relative to attachPhoneNumber, and the schema's carrier note implies a prior search call, but the description never states the prerequisite (searchPhoneNumbers first) or when to prefer this over importing a number. Usage is implied rather than spelled out.

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