Skip to main content
Glama
Sign In

eco-funding

by io.github.jdhart81
OverviewDiscussionsAdmin

Explain valuation

explain_valuation
Read-onlyIdempotent

Explain a valuation step by step: each quantity's formula, inputs, value, units, uncertainty and status (published method, v0.1 convention, input, or conjecture), plus limits. Accepts a valuation (receipt.result) or raw site inputs. Free rail.

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": {
      "valuation_or_site": "<valuation_or_site>"
    },
    "name": "explain_valuation"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuation_or_siteYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value by disclosing the status taxonomy (published method, v0.1 convention, input, conjecture) and the presence of stated limits, which tells the agent how to interpret results. "Free rail" hints at cost but is cryptic and unexplained.

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?

Two sentences, front-loaded with the verb and action; the field enumeration in the first sentence is dense but purposeful. "Free rail" is the only phrase that does not clearly earn its place without explanation.

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?

An output schema exists, so the return value need not be spelled out, and annotations cover the safety profile. The remaining gap is input-shape ambiguity on the sole untyped object parameter, which the description only partially resolves.

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 0% and the single parameter is a free-form object with additionalProperties=true, so the schema conveys nothing. The description partially compensates by naming two accepted input forms (a receipt.result valuation or raw site inputs), but it does not describe the expected shape, required fields, or how raw site inputs are distinguished from a valuation payload.

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 ("Explain a valuation step by step") and enumerates exactly what the explanation contains: formula, inputs, value, units, uncertainty, status, limits. This distinguishes it by verb semantics from compute-style siblings like value_site, though no sibling is named 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?

The line "Accepts a valuation (receipt.result) or raw site inputs" gives an input-mode hint that implies two calling contexts, but there is no explicit when-to-use guidance versus value_site or verify_receipt, and no statement of when this tool is the wrong choice.

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

All eco-funding 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