flowforge-mcp

flowforge_search_phone_numbers

Read-onlyIdempotent

Search purchasable phone numbers by country code, with optional area code and digit pattern filters, to find candidates for voice-agent or campaign setup.

Instructions

Search for available phone numbers that can be purchased.

Args: params: country_code, optional area_code and contains, limit.

Returns: JSON/Markdown listing candidate numbers available to buy.

Error Handling: Returns "Error: ..." on failure.

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": {
      "params": "<params>"
    },
    "name": "flowforge_search_phone_numbers"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds error behavior ('Returns "Error: ..." on failure') and the general return shape, which is modest added value beyond the annotations.

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?

The Args/Returns/Error Handling structure is easy to scan and the purpose sentence is front-loaded. The Args block largely duplicates schema content and could be trimmed, but nothing is verbose or padded.

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 annotations covering the safety profile, a rich nested input schema, and an output schema handling return values, the definition covers what is needed to call it correctly. The main missing piece is how results connect to the purchase/assign workflow, which matters for an agent acting on the candidates found.

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?

The description merely re-lists parameter names (country_code, area_code, contains, limit) with no formats or edge-case guidance. The nested schema already documents each field with examples ('415', '777', ISO codes) and defaults, so the description adds nothing beyond structured data.

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 gives a specific verb and resource ('Search for available phone numbers that can be purchased') and its qualifier 'available ... that can be purchased' implicitly separates it from listing already-owned numbers. It stops short of naming the closely related siblings such as flowforge_list_phone_numbers or flowforge_manage_phone_number, so the distinction is inferred rather than stated.

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 'that can be purchased' suggests this is a pre-purchase inventory lookup, but there is no explicit when-to-use versus flowforge_list_phone_numbers, flowforge_manage_phone_number, or flowforge_assign_phone_number, and no stated prerequisites or follow-up purchasing step. Usage context is implied only.

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

Deploy Server