Skip to main content
Glama

afro.tools

by io.github.afrotools
OverviewDiscussionsAdmin

Search Specs

search_specs
Read-onlyIdempotent

Searches specs by words and filters by category, channel, provider, country, currency, status or capability type. Returns the matching providers, each with its countries, currencies, sandbox flag, docs URL and the matching capabilities (name, type, status, example_prompt) — no endpoints, schemas, gotchas or canonical_example source. Use get_spec with the exact capability name to retrieve the full payload. A capability with "variants" has several request/response shapes (e.g. one per payment method or corridor): pass the ones you need to get_spec "variant" to receive only those.

Each result includes a "status" field:

  • "verified": tested against the provider's API, in "sandbox" or "production" (verified_in / verification.environment)

  • "deprecated": the provider is retiring it — get_spec says what replaces it

  • anything else (e.g. "ready", "unverified"): written from the provider's documentation, NOT tested against the live API — may contain errors

Always check the status field. If status is not "verified", inform the user that the spec is experimental and may contain errors.

Args:

  • query (string?): Words, e.g. "wave", "mobile money senegal", "send sms", "kyc", "XOF". Every word must match somewhere: provider name or slug, capability, description, example_prompt, countries (code or English/French name), currencies, channels (a few synonyms: momo, otp, kyc, payout…). Providers the query names come first.

  • category (string?): Filter by category, e.g. "payment", "communications" (SMS, WhatsApp, USSD, voice and email providers — "sms" is accepted as a legacy alias), "identity" (KYC, document verification, AML), "logistics" (delivery and courier providers). The registry adds categories over time: list_providers shows every category that exists

  • channel ("sms"|"whatsapp"|"ussd"|"voice"|"email"?): Only providers that offer this channel

  • provider (string?): Provider slug e.g. "paycard"

  • country_code (string?): ISO 3166-1 alpha-2 e.g. "GN"

  • currency (string?): ISO 4217 e.g. "XOF"

  • status ("verified"|"ready"|"unverified"?): e.g. "verified" for specs tested against the provider's API

  • capability_type ("synchronous"|"asynchronous"|"webhook"|"sdk"?): Filter by capability type

Returns: { providers: ProviderMatch[], note?: string, hint?: string, unverified_count: number, warning?: string } note is present when example_prompt was left out to keep a wide result readable. hint is present when nothing matched: widen the search before telling the user a provider is unavailable. unverified_count counts matching capabilities whose status is not "verified"; warning is present only when it is > 0.

Input Schema

NameRequiredDescriptionDefault
queryNoWords, e.g. "mobile money senegal" — every word must match
statusNo
channelNo
categoryNo
currencyNoISO 4217 e.g. "XOF"
providerNoProvider slug e.g. "paycard"
country_codeNoISO 3166-1 alpha-2 e.g. "GN"
capability_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare a safe idempotent read, and the description adds substantive context beyond them: what is deliberately excluded from results, the meaning of each status value with the strong 'not tested against live API, may contain errors' caveat, and the semantics of note, hint, unverified_count and warning in the response.

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?

Purpose is front-loaded and the Args/Returns structure is scannable, with almost every sentence carrying operational information. It is on the long side and repeats some return-shape detail, but nothing is filler-grade.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description fully documents the return object, its optional fields, and the interpretation rules for status — everything needed to call and interpret results for an 8-parameter, zero-required search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 50% schema coverage, the description compensates thoroughly: query is explained as all-words-must-match across named fields with provider ranking, category carries examples plus the legacy 'sms' alias and a discovery path via list_providers, and every other filter gets a concrete value example or definition. This clearly exceeds what the bare schema provides.

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?

Opens with a specific verb and resource ('Searches specs') plus the exact filter dimensions, and explicitly scopes what is omitted (no endpoints, schemas, gotchas, canonical_example) with a pointer to get_spec for the full payload. An agent can distinguish this from get_spec and list_providers without opening a schema.

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

Usage Guidelines5/5

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

Names the alternative explicitly ('Use get_spec with the exact capability name to retrieve the full payload') and gives the condition for it, plus how to handle variants via get_spec "variant". It also tells the agent to check the status field and inform the user when a spec is not verified, and the hint field tells it to widen the search rather than declare a provider unavailable.

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

All afro.tools 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