Skip to main content
Glama
Sign In

MangroveAI

by io.github.MangroveTechnologies
OverviewDiscussionsAdmin

list_approved_assets

Read-onlyIdempotent

List assets supported by platform ref-data, enriched with market data and risk scores. Approval is independent of risk assessment. Unassessed risk scores are null; do not interpret them as zero or infer regulatory approval. Returns available market metadata and risk scores.

[Access: pay 0.001 USDC via x402 (PAYMENT-SIGNATURE header) OR authenticate with an API key. An x402-capable client will auto-pay; API-key clients pay nothing per call.]

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

Input Schema

NameRequiredDescriptionDefault
top_nNoReturn only the first this many.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds genuinely new behavior: approval is orthogonal to risk scoring, unassessed risk is null rather than zero, and access requires either x402 payment (0.001 USDC) or an API key. That payment/authentication disclosure is real operational context an agent cannot get from annotations.

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?

The purpose is front-loaded in the first clause, the interpretation caveats follow, and the access/payment note is bracketed separately so it does not interrupt the main sentence. No padding, and the final 'Returns available market metadata and risk scores' is the only mildly redundant line.

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?

With no output schema, the description does the necessary work of saying what comes back (market metadata and risk scores) and how to read null risk values. For a zero-required-parameter list tool with annotations covering safety, the only remaining gap is ordering/default page size.

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?

There is a single optional parameter (top_n) with 100% schema description coverage, so the schema carries the burden and the baseline of 3 applies. The description adds nothing about top_n semantics or ordering beyond what the schema already says.

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: enumerating platform ref-data assets enriched with market data and risk scores. It is distinguishable from the singular get_asset, though it never names that or any other sibling explicitly as an alternative. The null/approval caveats reinforce what the listing actually contains.

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?

No explicit when-to-use or when-not-to-use guidance against siblings such as get_asset or screen_candidates. The description does give interpretive guidance ('Approval is independent of risk assessment', 'do not interpret null as zero'), which is useful but is about reading results rather than choosing this tool, so usage remains implied.

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

All MangroveAI 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