Skip to main content
Glama

aicomglobal

by io.github.moonspacenow-tech
OverviewAdmin

Run an Oasis service

aicom_run_service

Run one of the Oasis Toolkit services by id with an input object. Pass the id as service_id (alias service is also accepted) and its params as input. Returns a uniform envelope {ok, data, meta:{method, provenance, …}, error}. Free, deterministic, no signup. Discover ids with aicom_list_services.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNoThe service's input object (see aicom_describe_service for its shape)
serviceNoAlias for `service_id`.
service_idNoThe service id to run, e.g. 'json_repair'. Required unless you pass the alias `service`.

Schema Changelog

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

  1. Changed3 schema fields changed
    • addedInput schema / properties / service
      Added value: +{
+  "description": "Alias for `service_id`.",
+  "type": "string"
+}
    • changedInput schema / properties / service_id / description
      Previous value: -"The service id to run, e.g. 'json_repair'"New value: +"The service id to run, e.g. 'json_repair'. Required unless you pass the alias `service`."
    • removedInput schema / required
      Removed value: -[
-  "service_id"
-]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, description adds return envelope details, determinism, and freeness. Adequately informs agent of behavior beyond basic call.

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?

Four sentences, no redundancy, purpose front-loaded. Every sentence adds unique value.

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 no output schema or annotations, description explains return format, parameter usage, and discovery. Could mention error handling more but envelope covers it.

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

Parameters4/5

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

Schema coverage is 100%, but description adds alias clarification for service_id/service and references aicom_describe_service for input shape, adding value beyond schema.

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?

Clearly states it runs an Oasis service by ID with input. Distinguishes from sibling tools like aicom_list_services and aicom_describe_service by referencing them.

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?

Provides when-to-use context (free, deterministic, no signup) and points to discovery tools. Lacks explicit when-not-to-use, but given the generic nature, it's sufficient.

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