Skip to main content
Glama

Bay Run

by io.github.barneywohl

Run a public Bay Run Pin

run_pin

Run a public Bay Run Pin with just its input — {pin_id, input}. Canonical classification and Guard Pins also accept a bounded list of up to 8 strings; rows run through the existing scalar contract and return ordered per-row outcomes. max_price_usd and idempotency_key are OPTIONAL: omit max_price_usd to inherit the pin's mint ceiling; omit idempotency_key and a deterministic one is auto-minted from the input (retries replay from the durable Pin run authority across workers and restarts when configured). omit_raw_result is OPTIONAL and defaults to true for this MCP tool; set it false only when the receipt-bound raw result is required. REST keeps the same decision-first default; set it false for the explicit compatibility opt-in. max_price_usd is a hard per-call ceiling against the route's actual priced cost, never a promise to spend; successful zero-ceiling calls include receipt-bound per-row no_spend_evidence. Batch summaries make no aggregate no-spend claim unless every row receipt verifies. For the common retrieval loop, run the Guard Pin before generation or tool use, then run the Rerank Pin on retrieved documents before adding them to context. For canonical Pins, act on decision.action first; result is the preserved raw model output bound by the receipt when omit_raw_result=false. Known limits: guard is an English prompt-injection classifier (help docs may escalate; fail-closed); sentiment is SST-2 polarity only (a sarcasm cue abstains with sentiment_ambiguous_sarcasm; other irony can be confidently wrong); tickets returns exactly access_issue / billing_issue / delivery_issue or abstain, not a general classifier; rerank is a lexical TinyBERT demo, not semantic RAG, and its compact response always includes the rank order. Every Pin is provisional. Canonical aliases are guard, sentiment, tickets, and rerank; responses always return the underlying durable pin_id. Each scalar result includes its receipt-derived execution_id and a one-shot feedback URL/hint. The hint is write-authorized only for the authenticated execution credential that created that execution or an operator-attested owner evaluation credential; public demo, static, and OAuth bearers cannot submit feedback or corrections. Corrected or rejected held-out retention requires the exact receipt-bound input. Cross-Pin export or route changes still require evaluation:owner_write. Canonical pins callable with just {input}: prompt-injection guard route_00857aa05f863c2cdba0e908366b2cca; provisional sentiment route_1c7472e940dc02517f5af93792bf07ee; provisional ticket routing route_571826c40685073a99510b1951e60338; provisional document reranking route_f5411cdb31b03621742a58371fa95732. Free during launch: no card, no signup, no email. Mint a durable key with POST https://run.huggingbay.xyz/v1/keys/free

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesInput matching the pinned task.
pin_idYesPublic Pin id or canonical alias guard, sentiment, tickets, or rerank. Canonical ids and evidence labels are listed in the tool description.
max_price_usdNoOptional caller-authorized USD ceiling. Omit to inherit the pin's mint ceiling.
idempotency_keyNoOptional stable retry key. Omit and it is auto-minted from {pin_id, input}.
omit_raw_resultNoOptional decision-first projection. Defaults true for MCP; true omits the raw model result but retains decision and receipt evidence.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed2 schema fields changed
    • changedInput schema / properties / omit_raw_result / default
      Previous value: -falseNew value: +true
    • changedInput schema / properties / omit_raw_result / description
      Previous value: -"Optional decision-first projection. True omits the raw model result but retains decision and receipt evidence."New value: +"Optional decision-first projection. Defaults true for MCP; true omits the raw model result but retains decision and receipt evidence."
  2. Changed1 schema field changed
    • addedInput schema / properties / omit_raw_result
      Added value: +{
+  "default": false,
+  "description": "Optional decision-first projection. True omits the raw model result but retains decision and receipt evidence.",
+  "title": "Omit Raw Result",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / pin_id / description
      Previous value: -"Public Pin id. Canonical ids and evidence labels are listed in the tool description."New value: +"Public Pin id or canonical alias guard, sentiment, tickets, or rerank. Canonical ids and evidence labels are listed in the tool description."
  4. Changed1 schema field changed
    • changedInput schema / properties / pin_id / description
      Previous value: -"Public Pin id or canonical alias guard, sentiment, tickets, or rerank. Canonical ids and evidence labels are listed in the tool description."New value: +"Public Pin id. Canonical ids and evidence labels are listed in the tool description."
  5. Changed1 schema field changed
    • changedInput schema / properties / pin_id / description
      Previous value: -"Public Pin id. Canonical ids and evidence labels are listed in the tool description."New value: +"Public Pin id or canonical alias guard, sentiment, tickets, or rerank. Canonical ids and evidence labels are listed in the tool description."
  6. Changed1 schema field changed
    • changedInput schema / properties / pin_id / description
      Previous value: -"Public strong Pin id. Canonical ids are listed in the tool description."New value: +"Public Pin id. Canonical ids and evidence labels are listed in the tool description."
  7. Changed8 schema fields changed
    • addedInput schema / properties / idempotency_key / anyOf
      Added value: +[
+  {
+    "maxLength": 200,
+    "minLength": 8,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / idempotency_key / default
      Added value: +null
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Stable retry key."New value: +"Optional stable retry key. Omit and it is auto-minted from {pin_id, input}."
    • removedInput schema / properties / idempotency_key / maxLength
      Removed value: -200
    • removedInput schema / properties / idempotency_key / minLength
      Removed value: -8
    • removedInput schema / properties / idempotency_key / type
      Removed value: -"string"
    • changedInput schema / properties / pin_id / description
      Previous value: -"Public strong Pin id."New value: +"Public strong Pin id. Canonical ids are listed in the tool description."
    • changedInput schema / required
      Previous value: -[
-  "pin_id",
-  "input",
-  "idempotency_key"
-]New value: +[
+  "pin_id",
+  "input"
+]
  8. Changed7 schema fields changed
    • addedInput schema / properties / max_price_usd / anyOf
      Added value: +[
+  {
+    "maximum": 100,
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / max_price_usd / default
      Added value: +null
    • changedInput schema / properties / max_price_usd / description
      Previous value: -"Caller-authorized USD ceiling."New value: +"Optional caller-authorized USD ceiling. Omit to inherit the pin's mint ceiling."
    • removedInput schema / properties / max_price_usd / maximum
      Removed value: -100
    • removedInput schema / properties / max_price_usd / minimum
      Removed value: -0
    • removedInput schema / properties / max_price_usd / type
      Removed value: -"number"
    • changedInput schema / required
      Previous value: -[
-  "pin_id",
-  "input",
-  "max_price_usd",
-  "idempotency_key"
-]New value: +[
+  "pin_id",
+  "input",
+  "idempotency_key"
+]
  9. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries full responsibility for behavioral disclosure, and it delivers extensively. It reveals defaults, idempotency and retry behavior, hard price-ceiling semantics, per-row batch guarantees, feedback authorization constraints, retention requirements, and per-Pin known limits such as abstention cases and fail-closed behavior. This is highly transparent.

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 core invocation is front-loaded and nearly every sentence carries operational meaning. However, the description is extremely long, runs as one dense block, and includes semi-redundant or marginally relevant content such as REST parity notes and the free-key launch endpoint. It would benefit from headings, bullets, or separation of essential invocation from advanced caveats.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations, five parameters, an output schema, and significant behavioral nuance, this description is unusually complete. It covers invocation, optional parameters, workflow ordering, response components like decision.action and execution_id, authentication limits, known model limitations, and authorization requirements. An agent has enough context to invoke the tool correctly and interpret results.

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

Parameters5/5

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

The input schema already covers 100% of parameters, giving a baseline of 3, but the description substantially increases understanding of each parameter. It explains the consequence of omitting max_price_usd, deterministic auto-minting for idempotency_key, the MCP-specific default of omit_raw_result, and canonical aliases/route IDs for pin_id. This goes well beyond the schema text.

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 opening sentence clearly states a specific action and resource: run a public Bay Run Pin with {pin_id, input}. It also adds concrete detail on batch inputs, canonical classification, and Guard Pins. However, it never contrasts itself with the sibling tools coprocessor or solve_task, so full sibling differentiation is not present.

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?

The description provides explicit workflow guidance: run Guard before generation or tool use, run Rerank on retrieved documents before adding them to context, and act on decision.action first for canonical Pins. It also clarifies when to omit or set parameters like max_price_usd and idempotency_key. It lacks explicit alternatives or exclusion rules relative to the sibling tools, but within the tool's own domain the usage context is clear.

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

All Bay Run 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.

TDQS

A4.1/5.0
Disambiguation4/5

coprocessor is clearly distinct as a guard-before-action tool, while run_pin and solve_task both execute tasks and are differentiated mainly by whether a pin_id is known. The descriptions are verbose but do enough to separate the intent.

Naming Consistency2/5

run_pin and solve_task follow a verb_noun snake_case pattern, but coprocessor is a single noun with no verb, breaking the convention. The mix of noun-style and verb-style names creates inconsistency.

Tool Count4/5

Three tools is on the lean side but appropriate for an execution-focused server spanning guard, known-pin execution, and task routing without a pin_id. Each tool covers a distinct operation, though the extremely verbose descriptions make the set feel denser than the count suggests.

Completeness4/5

The core lifecycle of guarding, running a known pin, and routing an unknown task is covered. Minor gaps exist such as no tool for listing or inspecting pins, but the server's stated purpose is execution rather than pin management, so the coverage is mostly sufficient.

Resources