Skip to main content
Glama

kevaremesh

by io.github.cirralink-stack
OverviewDiscussionsAdmin

AI external APIs + Native Base64 x402 purchase — KEVAREMESH

kevaremesh_use
Destructive

Use for buyer-authorized Base64 encode/decode via the LIVE new x402 owned merchant (only if the current merchant release proof passes), and when a task needs fresh web search/content, news, finance, blockchain or crypto data, social search, people/business enrichment, geocoding, travel availability, AI/media generation, screenshots, weather, research, or another external API capability. Put only the desired result in goal; KEVAREMESH resolves the capability, compares eligible live x402 supply, adapts provider input, selects the provider, and routes execution. Discovery and quotes are free. Preparing an executable external route through this tool costs a $0.001 KEVAREMESH route fee. Upstream provider payments remain buyer-direct. Retry the same tool after each x402 PaymentRequired step.

Input Schema

NameRequiredDescriptionDefault
goalYesState only the result you need; do not search for, name, or choose an API/provider. Examples: search the web, retrieve blockchain/finance/news/social data, enrich an entity, geocode, run AI or media generation, search travel availability, take a screenshot, or check uptime.
inputNoFor owned API purchases, provide exact arguments, e.g. {text:'Hello',operation:'encode'} for Base64. Never put payment signatures in input.
previewNoIf true, only return a free validation/selection preview for a currently reviewed first-party product. No charge, execution or settlement is requested.
capabilityNoOptional explicit reviewed capability, e.g. base64_transform; unknown capabilities must still be resolved and the live merchant checked.
preferenceNoOptional free provider selection preference. Does not grant third-party execution rights.
continuationNoWhen payment credentials do not carry the KEVAREMESH continuation extension, resend only the exact continuation object returned by the previous PaymentRequired challenge. Never invent or edit route tokens.
max_budget_usdNoOptional maximum upstream provider spend for this task. If omitted, KEVAREMESH minimizes cost and the x402 client still controls whether any payment is authorized.
max_unit_price_usdNoOptional maximum price per upstream provider call. This is NOT a replacement for buyer-controlled x402 payment authorization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / continuation
      Added value: +{
+  "additionalProperties": true,
+  "description": "When payment credentials do not carry the KEVAREMESH continuation extension, resend only the exact continuation object returned by the previous PaymentRequired challenge. Never invent or edit route tokens.",
+  "type": "object"
+}
    • addedInput schema / properties / max_unit_price_usd
      Added value: +{
+  "description": "Optional maximum price per upstream provider call. This is NOT a replacement for buyer-controlled x402 payment authorization.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / preference
      Added value: +{
+  "description": "Optional free provider selection preference. Does not grant third-party execution rights.",
+  "enum": [
+    "balanced",
+    "cheapest",
+    "proven"
+  ],
+  "type": "string"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / capability
      Added value: +{
+  "description": "Optional explicit reviewed capability, e.g. base64_transform; unknown capabilities must still be resolved and the live merchant checked.",
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / input / description
      Previous value: -"Usually omit. Only add structured task fields when KEVAREMESH explicitly returns input_required."New value: +"For owned API purchases, provide exact arguments, e.g. {text:'Hello',operation:'encode'} for Base64. Never put payment signatures in input."
    • addedInput schema / properties / preview
      Added value: +{
+  "description": "If true, only return a free validation/selection preview for a currently reviewed first-party product. No charge, execution or settlement is requested.",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / goal / description
      Previous value: -"State only the outcome you need. Do not search for, name, or choose an API/provider yourself. Examples: search the web, get wallet/token data, retrieve finance/news/social data, enrich a person/company/email, geocode, run an LLM/image/TTS service, generate UUID v4 identifiers, convert units/time zones, validate JSON, search travel availability, take a screenshot, check uptime, or use another live API capability."New value: +"State only the result you need; do not search for, name, or choose an API/provider. Examples: search the web, retrieve blockchain/finance/news/social data, enrich an entity, geocode, run AI or media generation, search travel availability, take a screenshot, or check uptime."
  4. Changed1 schema field changed
    • changedInput schema / properties / goal / description
      Previous value: -"State only the outcome you need. Do not search for, name, or choose an API/provider yourself. Examples: search the web, get wallet/token data, retrieve finance/news/social data, enrich a person/company/email, geocode, run an LLM/image/TTS service, search travel availability, take a screenshot, check uptime, or use another live API capability."New value: +"State only the outcome you need. Do not search for, name, or choose an API/provider yourself. Examples: search the web, get wallet/token data, retrieve finance/news/social data, enrich a person/company/email, geocode, run an LLM/image/TTS service, generate UUID v4 identifiers, convert units/time zones, validate JSON, search travel availability, take a screenshot, check uptime, or use another live API capability."
  5. Changed2 schema fields changed
    • changedInput schema / properties / goal / description
      Previous value: -"State the outcome you need; do not choose a provider. Examples: search the web, get wallet/token data, check crypto risk or prices, retrieve finance/news/social data, enrich a person/company/email, geocode or look up IP/satellite data, generate an image, run an LLM, search travel availability, take a webpage screenshot, synthesize speech, check uptime, or search x402 resources."New value: +"State only the outcome you need. Do not search for, name, or choose an API/provider yourself. Examples: search the web, get wallet/token data, retrieve finance/news/social data, enrich a person/company/email, geocode, run an LLM/image/TTS service, search travel availability, take a screenshot, check uptime, or use another live API capability."
    • addedInput schema / properties / max_budget_usd
      Added value: +{
+  "description": "Optional maximum upstream provider spend for this task. If omitted, KEVAREMESH minimizes cost and the x402 client still controls whether any payment is authorized.",
+  "minimum": 0,
+  "type": "number"
+}
  6. Changed2 schema fields changed
    • removedInput schema / properties / continuation
      Removed value: -{
-  "additionalProperties": false,
-  "description": "Only use when returned by the previous kevaremesh_use call. Copy it unchanged so the same tool can continue provider payment or KEVAREMESH success-fee finalization.",
-  "properties": {
-    "execution_token": {
-      "type": "string"
-    },
-    "finalize_token": {
-      "type": "string"
-    },
-    "gateway_request_id": {
-      "type": "string"
-    },
-    "request": {
-      "additionalProperties": false,
-      "properties": {
-        "body": {},
-        "method": {
-          "default": "POST",
-          "enum": [
-            "GET",
-            "POST"
-          ],
-          "type": "string"
-        },
-        "query": {
-          "additionalProperties": {
-            "type": [
-              "string",
-              "number",
-              "boolean"
-            ]
-          },
-          "type": "object"
-        }
-      },
-      "type": "object"
-    },
-    "stage": {
-      "enum": [
-        "provider_payment",
-        "gateway_payment"
-      ],
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • changedInput schema / properties / input / description
      Previous value: -"Usually omit. Only add structured fields if KEVAREMESH returns input_required; copy the requested fields into this object."New value: +"Usually omit. Only add structured task fields when KEVAREMESH explicitly returns input_required."
  7. Changed9 schema fields changed
    • removedInput schema / properties / capability
      Removed value: -{
-  "description": "Optional capability override. Usually omit this; KEVAREMESH resolves the capability from goal.",
-  "type": "string"
-}
    • addedInput schema / properties / continuation / description
      Added value: +"Only use when returned by the previous kevaremesh_use call. Copy it unchanged so the same tool can continue provider payment or KEVAREMESH success-fee finalization."
    • changedInput schema / properties / goal / description
      Previous value: -"Describe the outcome you need. Example: get the USDC balance for an Ethereum wallet, search the web for fresh AI funding news, enrich a person, or fetch crypto market data."New value: +"State the outcome you need; do not choose a provider. Examples: search the web, get wallet/token data, check crypto risk or prices, retrieve finance/news/social data, enrich a person/company/email, geocode or look up IP/satellite data, generate an image, run an LLM, search travel availability, take a webpage screenshot, synthesize speech, check uptime, or search x402 resources."
    • changedInput schema / properties / input / description
      Previous value: -"Optional structured inputs for the chosen provider. If required fields are missing, KEVAREMESH returns the exact schema and asks you to call this same tool again."New value: +"Usually omit. Only add structured fields if KEVAREMESH returns input_required; copy the requested fields into this object."
    • removedInput schema / properties / max_total_upstream_usd
      Removed value: -{
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / max_unit_price_usd
      Removed value: -{
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / min_unique_payers_30d
      Removed value: -{
-  "default": 0,
-  "minimum": 0,
-  "type": "integer"
-}
    • removedInput schema / properties / preference
      Removed value: -{
-  "default": "balanced",
-  "enum": [
-    "balanced",
-    "cheapest",
-    "proven"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / preview
      Removed value: -{
-  "default": false,
-  "description": "If true, return the buyer-side provider decision and required input schema without creating a route session or payment challenge.",
-  "type": "boolean"
-}
  8. Added

TDQS

A3.8/5.0
Behavior4/5

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

With annotations already declaring openWorld=true, destructive=true, readOnly=false, and idempotent=false, the description adds substantial behavioral context: free discovery/quotes, a $0.001 route fee for executable external routes, buyer-direct upstream payments, and the PaymentRequired retry flow. It does not explicitly elaborate on destructiveness or non-idempotency, but the annotations already carry those safety signals.

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 description is front-loaded with the use case and follows with routing, pricing, and retry behavior. It is dense and jargon-heavy, especially around x402 and merchant release proof, but the length is largely justified by the broad meta-tool scope.

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

Completeness3/5

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

For an 8-parameter, open-world, potentially destructive routing/purchase tool with no output schema, the description covers the execution and payment flow well but does not explain what successful responses look like. It also lacks explicit sibling-tool differentiation, leaving some operational context incomplete.

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%, and every parameter is already documented. The description reinforces that goal should contain only the desired result and that input is for owned API purchases, but it largely repeats schema-level guidance rather than adding new parameter semantics.

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 clear capability-routing purpose: it resolves the requested external API capability, compares live x402 supply, selects a provider, and routes execution. It is much more specific than the name alone and lists concrete domains like Base64, web search, finance, and geocoding, though it does not explicitly distinguish itself from the sibling find/receipt/recover tools.

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

Usage Guidelines4/5

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

It gives clear usage context: use it when a task needs an external API capability, put only the desired result in goal, and retry the same tool after each x402 PaymentRequired step. It also states the merchant-release-proof condition and that discovery/quotes are free, but it does not explicitly compare when to choose the sibling tools instead.

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

All kevaremesh 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