Skip to main content
Glama
Sign In
@spoc/mcp-bridge

@spoc/mcp-bridge

Official
by SPOC-App
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Fetch public task metadata

spoc.task.get

Retrieve public task metadata by ID; for non-public tasks, return only ID, shape, execution mode, and status with prompt and result redacted.

Instructions

Return public task metadata by id. Non-public tasks return only the id, shape, execution_mode and status; prompt and result are redacted. Every task has a browsable record at /task/.

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": {
      "task_id": "<task_id>"
    },
    "name": "spoc.task.get"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose the redaction rule for non-public tasks (only id, shape, execution_mode and status survive), which is genuinely useful, but it says nothing about permission requirements, behavior for an unknown id, or rate limits on a fetch that could reasonably be called repeatedly.

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?

Three short sentences, front-loaded with the purpose, then the redaction caveat, then the browsable URL. No sentence is filler.

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

Completeness4/5

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

For a single-parameter read tool without an output schema, the description does the important work of naming the returned fields and explaining the redaction branch. It is only short of a complete picture on error behavior and how to acquire a task id.

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?

One parameter with 0% schema description coverage, so the schema adds nothing beyond type and length bounds. The phrase 'by id' signals that task_id is a task identifier, but no format, example, or source for obtaining a valid id is provided.

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?

States a specific verb and resource ('Return public task metadata by id') and scopes it to the public view. The resource (task) is plainly distinct from the harness.* siblings, though the description never names an alternative explicitly.

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?

There is no statement of when to choose this over harness.get or any other lookup, and no prerequisites are given. The only implicit signal is that the tool is an id-based fetch; the agent must infer the rest.

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

Deploy Server

Other Tools