Skip to main content
Glama
Sign In
Regen Network MCP Server

Regen Network MCP Server

by gaiaaiagent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

analyze_portfolio_impact

Evaluate the ecological impact of a portfolio by inputting a blockchain address. Select full analysis or a specific type to assess carbon and biodiversity assets.

Instructions

Advanced portfolio ecological impact analysis.

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": {
      "address": "<address>"
    },
    "name": "analyze_portfolio_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
analysis_typeNofull

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior1/5

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

With no annotations, the description must convey behavioral traits but only states 'advanced portfolio ecological impact analysis'. It does not indicate whether the tool is read-only, requires authentication, modifies state, or has any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (one brief sentence), but it is under-specified for the tool's apparent complexity. While concise, it sacrifices essential information.

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

Completeness1/5

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

Despite having an output schema, the description does not clarify what the analysis returns or how to interpret results. For a tool with 2 parameters and no annotations, the description fails to provide sufficient context to guide effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must add parameter meaning. However, it provides no explanation of the 'address' or 'analysis_type' parameters, leaving the AI agent without context on their roles or formats.

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?

The description clearly states the tool performs advanced portfolio ecological impact analysis, distinguishing it from siblings like analyze_market_trends by specifying the resource (portfolio ecological impact). However, it could be more specific about what the analysis entails.

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?

No guidance is provided on when to use this tool vs alternatives such as analyze_market_trends or compare_credit_methodologies. The description lacks context on prerequisites or when not to use it.

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