Skip to main content
Glama

assess onchain business

assess_onchain_business
Read-only

Assess an on-chain business from verifiable operating data (token usage, revenue, customer signals) with an evidence-backed risk grade, using FlowCredit on Finch. Returns the agent's official description, price, free runs, a run link and a ready-to-send request.

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

Input Schema

NameRequiredDescriptionDefault
taskNoOptional short description of what the user wants. Do not include private documents or secrets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered, but the description adds useful payload disclosure (returns official description, price, free runs, run link, ready-to-send request) – valuable given there is no output schema. However it is ambiguous whether the tool actually executes the assessment or merely returns a link plus a request to send, which is a material behavioral fact left unstated.

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 with the action front-loaded and no filler; the return-item enumeration is dense but earns its space since no output schema exists. Slightly overloaded with the parenthetical input list.

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

Completeness3/5

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

Because there is no output schema, the description rightly covers the return values, but it leaves the core ambiguity unresolved: is this an execution call producing a grade, or a discovery/preparation call returning an agent card and a request template? For an open-world third-party-backed tool, that distinction is essential for correct invocation.

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?

Only one optional parameter exists and the schema documents it at 100% coverage, including the privacy caveat about secrets, so the schema carries the burden. The description adds nothing about the task parameter but there is little left to add.

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 ("Assess an on-chain business") and enumerates the evidence inputs (token usage, revenue, customer signals) plus the output artifact (evidence-backed risk grade). It does not distinguish itself from risk-adjacent siblings like check_wallet_address_risk or trace_crypto_funds, which an agent could plausibly confuse it with.

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?

There is no statement of when to reach for this tool versus the other risk/analysis siblings, and no preconditions are given. The mention of "using FlowCredit on Finch" explains the mechanism, not the selection criteria, so an agent must infer the trigger case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.