Skip to main content
Glama

loadbay

by xyz.loadbay
OverviewDiscussionsAdmin

submit_harness

List a new harness on Loadbay. The repo MUST be a public, open-source GitHub repository. Optionally include a Base USDC address to receive tips. The listing appears immediately, tagged as community-added (unverified).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesharness name, e.g. my-coinbase-harness
repoYespublic GitHub repo URL — must be open source (have a license)
authorNoyour GitHub handle (defaults to the repo owner)
domainYesdomain key, one of: trading | coding | browser | productivity | data | social | health | science | gaming | media | robotics
traitsNocapability traits
summaryYeswhat it connects to, what tools it exposes, how an agent uses it
languageNoprimary language, e.g. TypeScript
integrationsNowhat it connects to, e.g. ["Coinbase","Slack"]
solanaAddressNoSolana wallet (base58) to receive USDC (SPL) tips — optional, alongside or instead of Base
baseUsdcAddressNoBase USDC wallet (0x…) to receive tips — only if you want to get paid

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description discloses key behavioral traits: listing appears immediately and is tagged as community-added (unverified). It could further mention uniqueness constraints or auth needs.

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?

Two concise sentences, front-loaded with the core action and essential conditions. No wasted words.

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?

Given 10 parameters and no output schema, the description covers the core purpose and key rule but omits details like domain enum values, trait meanings, or error handling.

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 100%, so baseline is 3. The description adds marginal context (e.g., why baseUsdcAddress is optional) but does not significantly enhance understanding beyond the 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?

The description clearly states the tool's action ('List a new harness on Loadbay') and distinguishes it from siblings like get_harness and search_harnesses through context.

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 provides essential usage requirements (repo must be public, open-source; optional tip address) but does not explicitly compare to sibling tools or state when not to use it.

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

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