Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

background_run

Run ANOTHER tool off the critical path: returns INSTANTLY while the target tool runs in the background, so a slow write/log/notify never delays your reply. Pass tool (the id of a tool you already have) and args (the target tool's arguments as a JSON object STRING). Optional serialize_key serializes background runs that share the key (e.g. the spreadsheet id when appending rows). Use ONLY for tools whose result you don't need this turn (logging, side-effect writes). Cannot run a tool you don't already have, cannot run a tool that requires approval, and cannot run a tool that deletes data — call those directly. Only callable from within an agent turn.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYesThe target tool's arguments as a JSON object STRING, e.g. '{"spreadsheet_id":"abc","values":[["a","b"]]}'. (A JSON string — not a bare object — so the schema stays valid for strict function-calling on voice.)
toolYesId of the tool to run in the background. Must be a tool you already have.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
serialize_keyNoOptional. Background runs sharing this key run one-at-a-time (e.g. pass the spreadsheet id when appending rows).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly=false, destructive=false, idempotent=false), but the description adds substantial context beyond them: instant return semantics, background execution model, the serialize_key serialization guarantee, and the approval/deletion restrictions. These are non-obvious behavioral traits that materially change how an agent invokes it.

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

Conciseness4/5

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

The most important constraint (instant background return) is front-loaded, and every sentence carries routing or constraint value. It is somewhat dense at five sentences, but there is little dead weight to cut.

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 fire-and-forget meta-tool with no output schema, the description fully covers what happens (instant return, background execution), what is prohibited, and the serialization option. An agent has everything needed to call it correctly without guessing.

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 the schema already documents all four parameters including the JSON-string rationale and serialize_key example. The description restates 'tool must be a tool you already have' and the serialize_key example rather than adding new meaning, so it sits at the schema-driven baseline.

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 lead sentence states a specific verb (run) and resource (another tool) plus the key behavioral trait (returns INSTANTLY). An agent can immediately distinguish this meta-tool from every direct sibling in the list, since it operates on other tools rather than a domain resource.

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

Usage Guidelines5/5

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

Explicit when-to-use ('Use ONLY for tools whose result you don't need this turn (logging, side-effect writes)') and when-not-to-use ('cannot run a tool that requires approval, and cannot run a tool that deletes data — call those directly'). This is a near-complete routing rule with the alternative action named.

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

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