Skip to main content
Glama
Sign In

site

by com.proofzo
OverviewDiscussionsAdmin

Where this data comes from, and how to cite it

dataset_provenance

The source, the date it was computed, the licence and the citation for the Proofzo dataset. Read this to attribute a figure correctly.

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": "dataset_provenance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

There are no annotations, so the description carries the behavioral burden. It transparently enumerates the provenance fields a caller can expect and implies a read-only metadata lookup, with no side effects or hidden behavior. It does not describe the exact return shape, but for a zero-parameter metadata tool this is acceptable.

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 the key facts and ending with a clear action directive. Every word earns its place, and there is no redundant restating of the tool name.

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 simple, zero-parameter metadata look-up, the description is complete: an agent knows what data it will get, why it matters, and when to call it. No output schema is needed to make a correct call.

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 has zero parameters, so there is nothing to explain beyond the baseline. The description still usefully clarifies what fields the returned provenance contains, compensating for the lack of an output 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 names a specific resource ('the Proofzo dataset') and a concrete purpose ('attribute a figure correctly'), listing the exact fields it covers: source, compute date, licence, and citation. This clearly distinguishes it from sibling tools that provide columns, rows, stats, or search.

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 states when to use it: 'Read this to attribute a figure correctly.' It does not explicitly name alternatives or exclusions, but the sibling set makes the scoping obvious enough for an agent to select it for citation/provenance questions.

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

All site toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources