Skip to main content
Glama

KEVAREMESH AI Procurement Gateway

by io.github.cirralink-stack
OverviewDiscussionsAdmin

One tool to discover or use rights-compatible external APIs

kevaremesh_use_infrastructure

One agent-facing entry to the rights-verified bounded external API catalog (Frankfurter, USGS, Crossref and ROR where currently enabled). Read the live catalog to discover available operations. Actions: catalog, execute, batch, resolve, pass_catalog and paid_execute. Free operations remain bounded. A buyer-authorized x402 24h Access Pass supports independently verified paid admission with capped immediate API execution; the MCP tool does not sign, buy, or move funds. It cannot perform purchases, send funds, forward arbitrary URLs or execute upstream fee-bearing APIs. The live catalog combines current first-party products and rights-eligible external operations when independent checks succeed; inventory counts are not hardcoded.

Input Schema

NameRequiredDescriptionDefault
goalNo
jobsNo
inputNoFor currency_rate: base/quote ISO codes; for currency_convert add amount; currency_history add date; USGS operations use empty object; Crossref DOI lookup requires doi, publication search requires query; ROR organization search uses query and ROR record uses id. Always consult the live catalog for exact schemas.
actionNocatalog
operationNoUse an exact operation name returned by action=catalog. The hub enforces permitted operations, original inputs and per-provider rights before use.
access_keyNoFor paid_execute only: the buyer-held 32-byte random access key from an independently confirmed x402 Access Pass. Treat as private; never expose in public logs or chat.
request_idNoOptional paid_execute logical invocation key. Reuse exactly on retries; a new key refreshes live data. Omission caches identical operation/input per pass.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request_id
      Added value: +{
+  "description": "Optional paid_execute logical invocation key. Reuse exactly on retries; a new key refreshes live data. Omission caches identical operation/input per pass.",
+  "pattern": "^[0-9a-f]{64}$",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / access_key
      Added value: +{
+  "description": "For paid_execute only: the buyer-held 32-byte random access key from an independently confirmed x402 Access Pass. Treat as private; never expose in public logs or chat.",
+  "pattern": "^[0-9a-f]{64}$",
+  "type": "string"
+}
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "catalog",
-  "execute",
-  "batch",
-  "resolve"
-]New value: +[
+  "catalog",
+  "execute",
+  "batch",
+  "resolve",
+  "pass_catalog",
+  "paid_execute"
+]
  3. Changed4 schema fields changed
    • changedInput schema / properties / input / description
      Previous value: -"For currency_rate: base/quote ISO codes; for currency_convert add amount; currency_history add date; USGS operations use empty object; Crossref DOI lookup requires doi, publication search requires query."New value: +"For currency_rate: base/quote ISO codes; for currency_convert add amount; currency_history add date; USGS operations use empty object; Crossref DOI lookup requires doi, publication search requires query; ROR organization search uses query and ROR record uses id. Always consult the live catalog for exact schemas."
    • addedInput schema / properties / operation / description
      Added value: +"Use an exact operation name returned by action=catalog. The hub enforces permitted operations, original inputs and per-provider rights before use."
    • removedInput schema / properties / operation / enum
      Removed value: -[
-  "currency_rate",
-  "currency_convert",
-  "currency_history",
-  "currency_currencies",
-  "earthquake_m45_day",
-  "earthquake_significant_week",
-  "crossref_doi_lookup",
-  "crossref_search_publications"
-]
    • addedInput schema / properties / operation / pattern
      Added value: +"^[a-z][a-z0-9_]{1,80}$"
  4. Changed2 schema fields changed
    • changedInput schema / properties / input / description
      Previous value: -"For currency_rate: base/quote ISO codes; for currency_convert add amount; currency_history add date; USGS operations use empty object."New value: +"For currency_rate: base/quote ISO codes; for currency_convert add amount; currency_history add date; USGS operations use empty object; Crossref DOI lookup requires doi, publication search requires query."
    • changedInput schema / properties / operation / enum
      Previous value: -[
-  "currency_rate",
-  "currency_convert",
-  "currency_history",
-  "currency_currencies",
-  "earthquake_m45_day",
-  "earthquake_significant_week"
-]New value: +[
+  "currency_rate",
+  "currency_convert",
+  "currency_history",
+  "currency_currencies",
+  "earthquake_m45_day",
+  "earthquake_significant_week",
+  "crossref_doi_lookup",
+  "crossref_search_publications"
+]
  5. Added

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the MCP tool does not sign, buy, or move funds; cannot purchase, send funds, forward arbitrary URLs, or execute fee-bearing upstream APIs; free operations are bounded; paid access requires an independently verified x402 Access Pass; and the catalog is live rather than hardcoded. It still omits error behavior, rate limits, and response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and most sentences add a real constraint, but the prose is dense with repeated rights/jargon language ('rights-verified', 'rights-compatible', 'rights-eligible') and long compound clauses that reduce scannability.

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 a complex 7-parameter tool with nested objects and no output schema, the description covers purpose and payment/security boundaries but leaves major gaps: how to choose between its actions, how the parameters interact, and what results or errors to expect. It is adequate but incomplete.

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

Parameters2/5

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

Schema description coverage is only 57%, so the description should compensate, but it does not explain goal, jobs, input structure, action semantics, or request_id behavior beyond what the schema already contains. It mentions paid_execute and access_key only obliquely by describing the Access Pass, not the parameters themselves.

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 specific verb and resource: an agent-facing entry point to a rights-verified external API catalog with actions catalog/execute/batch/resolve/pass_catalog/paid_execute. It clearly says what the tool is, but it does not distinguish itself from siblings such as kevaremesh_auto_use or kevaremesh_route_intent, leaving overlap ambiguous.

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?

It implies usage: 'Read the live catalog to discover available operations' suggests catalog-first, and it separates free bounded operations from buyer-authorized paid_execute. However, there is no explicit when-to-use-this-vs-alternative guidance against the many sibling tools, so the agent must infer routing.

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

All KEVAREMESH AI Procurement Gateway 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