Skip to main content
Glama

aicomglobal

by io.github.moonspacenow-tech
OverviewAdmin

Find a trusted service/API/tool for a task

aicom_search_offerings

Find a trusted, verified service, API, tool, or MCP/A2A endpoint to call or delegate to for a task — ranked by a transparent trust score, each with the lister's verification tier. The safe way to discover what to use mid-task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryNoWhat you are looking for, e.g. 'real-time price data' or 'image generation'. OMIT to browse ALL listings ranked by trust (paginate with limit).
categoryNoOptional category filter, e.g. 'data', 'generation', 'research'
min_trustNoOnly return offerings at or above this trust band

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / min_trust / enum
      Previous value: -[
-  "untrusted",
-  "low",
-  "medium",
-  "high"
-]New value: +[
+  "untrusted",
+  "unclaimed",
+  "low",
+  "medium",
+  "high"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"What you are looking for, e.g. 'real-time price data' or 'image generation'"New value: +"What you are looking for, e.g. 'real-time price data' or 'image generation'. OMIT to browse ALL listings ranked by trust (paginate with limit)."
    • removedInput schema / required
      Removed value: -[
-  "query"
-]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It notes the tool returns results ranked by trust score and verification tier, suggesting a read-only search. However, it does not explicitly state whether the tool is read-only, has side effects, or requires authentication. The description is adequate but lacks full transparency.

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

Conciseness5/5

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

The description consists of two concise sentences. The first sentence immediately states the core functionality and ranking criteria. The second sentence reinforces the safe discovery use case. Every word adds value, and the structure is front-loaded with key information.

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?

Given the tool has 4 parameters (none required), no output schema, and no annotations, the description is fairly complete. It explains the purpose, ranking, and trust aspect. However, it does not describe the return format (e.g., list of offerings with scores and tiers) or pagination behavior implied by the limit parameter. Slight gap, but still nearly complete.

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%, so each parameter (limit, query, category, min_trust) is well-documented in the input schema. The tool description adds no additional meaning beyond the schema's parameter descriptions. According to guidelines, baseline 3 is appropriate when schema coverage is high.

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?

The description clearly states the tool finds trusted, verified services, APIs, tools, or endpoints ranked by trust score. The verb 'Find' and specific resources (service, API, tool, endpoint) with a clear purpose (delegate a task) make it highly specific and distinguishable from siblings like aicom_list_services or aicom_get_offering.

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 description implies usage for mid-task discovery ('The safe way to discover what to use mid-task'), but does not explicitly state when to use this tool over siblings such as aicom_list_services or aicom_describe_service. No alternatives or exclusions are provided, so the guidance is clear but incomplete.

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

All aicomglobal toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources