Skip to main content
Glama
Ge-Shun

origin-mcp

by Ge-Shun
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

origin_bridge_task_status

Check the status, retrieve results, and optionally view recent logs of a background task submitted to the Origin bridge.

Instructions

Read status, result, or optional recent logs for an Origin bridge background task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoOptional Origin bridge host override. Normally omit to use configured localhost.
portNoOptional Origin bridge TCP port override. Normally omit to use the handshake value.
tokenNoOptional bridge authentication token override. Normally omit to use the handshake.
task_idYesBackground task identifier returned by origin_bridge_submit_task.
timeoutNoBridge request timeout in seconds; null uses the configured default.
log_limitNoMaximum number of recent background-task log records to return.
include_logsNoWhether to include recent background-task log records in the response.
include_resultNoWhether to include a completed background task's result payload.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed8 schema fields changedv0.1.3
    • addedInput schema / properties / host / description
      Added value: +"Optional Origin bridge host override. Normally omit to use configured localhost."
    • addedInput schema / properties / include_logs / description
      Added value: +"Whether to include recent background-task log records in the response."
    • addedInput schema / properties / include_result / description
      Added value: +"Whether to include a completed background task's result payload."
    • addedInput schema / properties / log_limit / description
      Added value: +"Maximum number of recent background-task log records to return."
    • addedInput schema / properties / port / description
      Added value: +"Optional Origin bridge TCP port override. Normally omit to use the handshake value."
    • addedInput schema / properties / task_id / description
      Added value: +"Background task identifier returned by origin_bridge_submit_task."
    • addedInput schema / properties / timeout / description
      Added value: +"Bridge request timeout in seconds; null uses the configured default."
    • addedInput schema / properties / token / description
      Added value: +"Optional bridge authentication token override. Normally omit to use the handshake."
  2. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / include_logs
      Added value: +{
+  "default": false,
+  "title": "Include Logs",
+  "type": "boolean"
+}
    • addedInput schema / properties / include_result
      Added value: +{
+  "default": true,
+  "title": "Include Result",
+  "type": "boolean"
+}
    • addedInput schema / properties / log_limit
      Added value: +{
+  "default": 20,
+  "title": "Log Limit",
+  "type": "integer"
+}
  3. Added

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It states 'Read' suggesting non-destructive behavior, but does not disclose potential behaviors like error handling, blocking nature, or prerequisites. The description is too brief to convey behavioral traits beyond the basic read action.

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?

Single sentence, no wasted words. The key information is front-loaded. Every word serves a purpose.

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?

With 8 parameters and an output schema, the description is minimal. It does not explain parameter interdependencies (e.g., log_limit effect when include_logs is false) or scenarios. However, the presence of an output schema reduces the need to describe return values, keeping the score at a mid level.

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 3. The description does not add new meaning beyond what the schema already provides for each parameter. It mentions 'status, result, or optional recent logs' which aligns with include_result and include_logs, but the schema covers those details.

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 uses the specific verb 'Read' and clearly identifies the resource as 'status, result, or optional recent logs for an Origin bridge background task'. It effectively distinguishes from sibling tools like origin_bridge_cancel_task and origin_bridge_list_tasks.

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?

No explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., after submitting a task) or when not to use it. The description implies checking task status but lacks comparative context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Ge-Shun/origin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server