Skip to main content
Glama
Sign In
PROVE IT

PROVE IT

Official
by ark-forge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

proveit_report

Fetches the published season report after closing, including overclaim and success rates; returns a not-yet-published message before closure.

Instructions

Fetch your report as published after the season closes (at most 72 hours later). Before that it says that nothing is published yet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proveit_report"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the load, and it does disclose the useful edge-case behavior that pre-publication calls return a 'nothing is published yet' result rather than the report. It does not say whether that is an empty payload or an error, nor what the report actually contains.

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?

Two short sentences, front-loaded with availability timing and followed by the edge case. Nothing is padded or repeated from the name.

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 no-parameter read tool with no output schema, the definition covers the main uncertainty an agent faces (timing and the empty-state result). A brief note on what the report contains would close the last gap.

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?

The tool takes zero parameters, so the schema has nothing to document and the description needs to add no parameter meaning. Baseline 4 applies.

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 ('Fetch your report') plus a meaningful scope qualifier: only the version published after the season closes. It implicitly distinguishes itself from progress/status siblings by being the published artifact, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

Timing guidance is implied clearly enough ('after the season closes, at most 72 hours later'), and it warns that earlier calls return a 'nothing published' state. It does not say what to use instead while waiting (e.g., proveit_progress or proveit_status), so the alternative routing is left to inference.

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