Skip to main content
Glama
Sign In

Gluo

by dev.gluo
OverviewDiscussionsAdmin

Call a Gluo service

call_api

Make one call. Leave out budgetId to use the free tier (free operations only, daily allowance). Input must match the operation's schema exactly (extra fields are rejected). Paid calls are charged only if the answer passes Gluo's output check; repeating an identical call shortly after is free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service": "<service>",
      "operation": "<operation>",
      "input": "<input>"
    },
    "name": "call_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
serviceYes
budgetIdNoOmit for free-tier calls
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

The description adds substantial behavioral context beyond the sole openWorldHint annotation: free-tier daily allowances, strict rejection of extra input fields, paid charging only after an output check passes, and short-term idempotency for identical calls. It still omits authentication and rate-limit behavior, so it is strong but not exhaustive.

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 compact sentences, each carrying distinct operational information: invocation scope, free-tier routing, input validation strictness, and billing/idempotency. No repetition or filler.

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?

The tool has nested free-form input, no output schema, and open-world behavior, yet the description does not explain return values, error behavior on failed output checks, or how to discover service and operation identifiers. It is adequate for billing and validation rules but incomplete for end-to-end invocation.

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 25%, and the description meaningfully clarifies budgetId omission and the strict "input must match exactly" rule. However, it says nothing about valid values or discovery paths for service and operation, so it only partially compensates for the low schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Make one call" is vague about what is actually being invoked; the title identifies it as a Gluo service call, but the description never defines a call as an operation on a service or distinguishes it from sibling tools like list_services or request_service. An agent can infer the general purpose but not the concrete resource semantics.

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

Usage Guidelines2/5

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

It explains the budgetId/free-tier condition but gives no guidance on when to use this tool versus alternatives such as list_services, request_service, or budget tools. There is no stated prerequisite that service and operation names must first be discovered through sibling tools.

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

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