Skip to main content
Glama
0xddneto

AI Proof of Us MCP Server

by 0xddneto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

estimate_ai_reward

Read-onlyIdempotent

Estimate the AIPOU token reward for an AI-assisted task before submitting it. Provide input tokens, output tokens, and duration to get an informational reward estimate without creating a receipt or changing state.

Instructions

Use before complete_ai_task only when a preview is useful. Provide non-negative inputTokens, outputTokens, and durationSeconds for one task; it returns JSON with estimatedReward and unit for a client-signed estimate. It creates no task or receipt, changes no state, and submits no transaction. The result is informational: complete_ai_task derives the receipt evidence, and the validator determines final eligibility and trust tier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputTokensYesNon-negative input-token count for this task, capped at 10,000,000.
outputTokensYesNon-negative output-token count for this task, capped at 10,000,000.
durationSecondsYesTask duration in whole seconds from 0 through 86,400.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / durationSeconds / description
      Added value: +"Task duration in whole seconds from 0 through 86,400."
    • addedInput schema / properties / inputTokens / description
      Added value: +"Non-negative input-token count for this task, capped at 10,000,000."
    • addedInput schema / properties / outputTokens / description
      Added value: +"Non-negative output-token count for this task, capped at 10,000,000."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, but the description adds specificity: it enumerates what the call does not do (creates no task or receipt, changes no state, submits no transaction) and that the result is informational rather than final. That goes well beyond a generic readOnlyHint with actionable nuance about a client-signed estimate.

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 dense, ordered sentences front-load the rule ('Use before complete_ai_task only when a preview is useful') and keep every subsequent sentence purposeful: parameter/behavior constraints, then scope and authority. No filler or repetition exists.

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 three-parameter, read-only tool with 100% schema coverage, the description tells the agent what it returns (JSON estimate with estimatedReward and unit), when in the workflow to call it (before completion), and why the result is non-binding. Given the output schema is absent and annotations carry the safety profile, no essential info is missing.

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 condition is 100%, and each parameter already has names, types, bounds, and descriptions. The description only mirrors 'non-negative' scoping, so it adds no semantic information over the schema. Baseline 3 is appropriate.

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?

Description states a precise verb (estimate) and resource (reward for AI task), and — critically — distinguishes it from its near-sibling complete_ai_task by noting it produces no receipt or state change. It also says exactly what it returns (JSON with estimatedReward and unit), so an agent can select it without studying the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The opening clause is explicit about timing and selection: 'Use before complete_ai_task only when a preview is useful.' It also names the authoritative alternative (complete_ai_task derives the receipt evidence; the validator determines final eligibility), letting an agent know when it is NOT a substitute.

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