Skip to main content
Glama
Sign In
ClockNext MCP Server

ClockNext MCP Server

Official
by Clocknext-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ClockNext: get outcome

clocknext_get_outcome
Read-only

Retrieve a complete outcome type by ID, including its steps and real-time in-flight and completed statistics.

Instructions

Get one outcome type in full by id — its steps plus in-flight/completed stats.

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>"
    },
    "name": "clocknext_get_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe outcome id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds behavioral context about what is returned (steps and stats). This goes beyond the annotations by clarifying the response content, though it doesn't describe pagination or error conditions.

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?

The description is a single, front-loaded sentence that conveys all essential information without unnecessary words or repetition. It is concise and well-structured.

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 simple get-by-id tool with one parameter and no output schema, the description provides sufficient context about the return value (steps and stats) to orient the agent. It could be more explicit about the format of stats, but overall it's complete for the tool's complexity.

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% with a clear description for the 'id' parameter. The tool description adds no additional meaning beyond 'by id', which is already implied by the parameter name and schema.

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 clearly states the tool gets 'one outcome type in full by id' with specific content ('steps plus in-flight/completed stats'). This distinguishes it from sibling tools like clocknext_list_outcomes, which presumably list multiple outcomes without full detail.

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 implies use for a single outcome type by id, contrasting with list operations. It provides clear context for when to use the tool, though it doesn't explicitly name alternatives or exclusion scenarios.

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