Skip to main content
Glama

KEVAREMESH AI Procurement Gateway

Search the global AI API department store

kevaremesh_search_marketplace
Read-onlyIdempotent

Unified free cross-directory search of KEVAREMESH-owned products, 11 rights-scoped executable external Hub operations, public x402 listings, an automatic official MCP registry index, and an MIT-licensed public API directory. Search listings are not supplier execution rights or verified payable quotes. Do not pay or proxy an external listing solely because it appears here. For runnable rights-scoped results use kevaremesh_use_infrastructure. For owned purchases use kevaremesh_auto_use with buyer-signed x402 authorization.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kevaremesh_search_marketplace"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoAPI function, goal, provider or operation keyword; empty lists available inventory.
sourceNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "all",
      -  "external",
      -  "kevaremesh_owned",
      -  "kevaremesh_infrastructure",
      -  "agent402",
      -  "agent_bazaar",
      -  "mcp_registry"
      -]New value: +[
      +  "all",
      +  "external",
      +  "kevaremesh_owned",
      +  "kevaremesh_infrastructure",
      +  "agent402",
      +  "agent_bazaar",
      +  "mcp_registry",
      +  "mcp_registry_index",
      +  "public_api_mit"
      +]
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the bar is lower, yet the description adds a genuinely important trust caveat: listings are not execution rights or verified payable quotes and must not be paid on appearance alone. It stops short of describing result shape or ranking behavior, but the critical safety warning is present.

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 opening sentence is overloaded with stacked clauses and an unexplained count ("11 rights-scoped executable external Hub operations"), and the label "department store" in the title adds little. The two follow-on sentences are tight and well-placed safety/routing guidance.

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 open-world, zero-required-parameter search with no output schema, an agent still needs to know what a result record contains and how the source enum partitions results; the description covers purpose, trust limits and routing but omits return-shape and result-differentiation detail.

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 coverage is only 33%: query is documented in the schema, but limit (1-30, default 20) and the nine-value source enum have no descriptions anywhere. The description's list of corpora loosely hints at what source values select (external, kevaremesh_owned, kevaremesh_infrastructure, agent402, mcp registry, public_api_mit) but never maps them or explains inventory-listing behavior beyond the schema's empty-query note.

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 names a specific verb and resource ("Unified free cross-directory search") and enumerates the five corpora it covers (KEVAREMESH-owned products, external Hub operations, x402 listings, MCP registry index, MIT directory). It separates itself from execution siblings by explicitly noting results are "not supplier execution rights or verified payable quotes," though the dense jargon and the odd count "11 rights-scoped" slightly blur the core statement.

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?

It gives explicit negative guidance ("Do not pay or proxy an external listing solely because it appears here") and routes to two named alternatives with their conditions: kevaremesh_use_infrastructure for runnable rights-scoped results and kevaremesh_auto_use for owned purchases with buyer-signed x402 authorization. This is close to a complete routing decision tree.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources