Skip to main content
Glama

report_outcome

Report job execution outcomes to the Maiat trust oracle, providing real data on success, failure, partial completion, or expiration status.

Instructions

Report the outcome of a job after executing it. This feeds the Maiat trust oracle with real outcome data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdYesThe job ID to report outcome for
outcomeYesThe outcome of the job
reporterNoAddress of the reporter (optional)
noteNoFree-form note about the outcome (optional)

Implementation Reference

  • The MCP tool definition and handler for 'report_outcome' in the mcp-server package. It parses the inputs and calls the SDK's reportOutcome method.
    server.tool(
      "report_outcome",
      "Report the outcome of a job after executing it. This feeds the Maiat trust oracle with real outcome data.",
      {
        jobId: z.string().describe("The job ID to report outcome for"),
        outcome: z
          .enum(["success", "failure", "partial", "expired"])
          .describe("The outcome of the job"),
        reporter: z
          .string()
          .optional()
          .describe("Address of the reporter (optional)"),
        note: z
          .string()
          .optional()
          .describe("Free-form note about the outcome (optional)"),
      },
      async ({ jobId, outcome, reporter, note }) => {
        try {
          const data = await sdk.reportOutcome({
            jobId,
            outcome,
            reporter: reporter ?? undefined,
            note: note ?? undefined,
          });
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(data, null, 2),
              },
            ],
          };
  • The underlying SDK implementation of reportOutcome, which sends a POST request to the Maiat API.
    async reportOutcome(params: OutcomeParams): Promise<OutcomeResult> {
      return this.request<OutcomeResult>("/api/v1/outcome", {
        method: "POST",
        body: JSON.stringify(params),
      });
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions feeding a 'trust oracle' but doesn't disclose key behavioral traits: whether this is a write operation (implied by 'Report'), if it requires authentication, potential side effects (e.g., updating trust scores), rate limits, or error handling. The description is too vague to guide safe and effective use.

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 description is concise with two sentences that directly state the tool's purpose and high-level goal. It's front-loaded with the core action. However, the second sentence about the 'trust oracle' could be more integrated or omitted if redundant, but it adds useful context without excessive verbosity.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a tool with 4 parameters and mutation implications ('Report'). It lacks details on behavioral traits, usage context, and return values. For a tool that likely updates a trust system, more guidance on permissions, effects, and error cases is needed to be fully helpful.

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 fully documents parameters. The description adds no parameter-specific semantics beyond implying 'jobId' and 'outcome' are required for reporting. It doesn't explain the meaning of 'reporter' address or 'note' context, nor does it clarify the enum values (e.g., what 'partial' or 'expired' mean). Baseline 3 is appropriate since the schema does the heavy lifting.

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?

The description clearly states the action ('Report') and the target ('outcome of a job'), and mentions the purpose ('feeds the Maiat trust oracle with real outcome data'). It distinguishes from siblings by focusing on job outcome reporting rather than analysis, reputation checks, or other operations. However, it doesn't explicitly differentiate from all siblings (e.g., 'submit_review' might be conceptually similar).

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?

The description provides minimal guidance: it implies use after job execution to report outcomes. No explicit when-not-to-use conditions, prerequisites, or alternatives are mentioned. For example, it doesn't clarify if this should be used instead of 'submit_review' for job-related outcomes or how it interacts with other trust-related tools like 'get_agent_trust'.

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/JhiNResH/maiat-protocol'

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