Skip to main content
Glama

OpenCurrent

따라 해 본 결과 알리기

report_outcome
Idempotent

get_workflow로 받은 워크플로를 실제로 따라 한 뒤 결과를 알릴 때 사용. success(목표대로 됨), partial(일부만 됨), failure(안 됨)와 짧은 이유, 쓴 모델을 남기면 이 워크플로의 평가 점수에 반영. OpenCurrent 무료 키 필요. 내용은 바뀌지 않음. 같은 키는 워크플로마다 하루 한 번(다시 보내면 그날 보고를 바꿈).

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": {
      "id": "<id>",
      "outcome": "<outcome>"
    },
    "name": "report_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes워크플로 id (get_workflow의 id)
modelNo따라 할 때 쓴 모델 이름
reasonNo무엇이 잘 됐거나 막혔는지 한두 문장. 사용자 개인정보는 넣지 말 것
outcomeYes

Output Schema

NameRequiredDescriptionDefault
messageYes
recordedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the auth requirement (OpenCurrent free key), the rate limit (one report per key per workflow per day), the overwrite semantics of a resend, the downstream side effect (it feeds into the workflow's evaluation score), and that the workflow content itself is not modified. This is exactly the kind of context annotations cannot carry.

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?

A single dense paragraph that leads with the usage trigger before constraints and side effects. Every clause carries information; the only slightly opaque line is 'content does not change', which requires the reader to infer it refers to workflow content rather than the report.

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 small four-parameter write tool with an output schema, annotations, and 75% schema coverage, everything an agent needs to call it correctly is present: trigger, auth, rate limit, idempotency behavior, side effect, and enum semantics.

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

Parameters4/5

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

Schema coverage is 75%, so the baseline is 3; the description earns an upgrade by defining the enum's meaning in plain terms (success = goal met as intended, partial = only partly, failure = not met) and by explaining that model records the model used and reason is a short account. It does not restate the id parameter or the privacy constraint already in the schema, which is correct.

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: report the outcome after actually following a workflow obtained from get_workflow, naming the source sibling and the three outcome values. An agent can distinguish this reporting tool from the retrieval siblings without opening the schema, though it does not explicitly say what it is NOT for.

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?

Gives a clear trigger condition ('after you have actually followed the workflow received from get_workflow and want to report the result') and operational constraints: free OpenCurrent key required, once per day per workflow, and resending replaces that day's report. No explicit exclusion cases, but the preconditions are concrete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources