Skip to main content
Glama
enesjakozh
Codeshark-NET

ClimateTriage MCP Server

by Codeshark-NET
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

ClimateTriage MCP サーバー

ClimateTriage API と統合され、気候変動と持続可能性に関連するオープンソースの問題を検索するためのツールを提供する MCP サーバー実装。

特徴

  • 問題検索: 気候関連プロジェクトのオープンソースの問題を見つける

  • 複数のフィルター: カテゴリ、プログラミング言語、キーワードなどでフィルターします

  • 並べ替えオプション: 作成日、更新日、星の数で問題を並べ替えます

Related MCP server: GitHub Issues MCP Server

ツール

気候問題の検索

気候変動と持続可能性に関連するオープンソースの問題を検索します。

入力:

  • category （文字列、オプション）：プロジェクトカテゴリで問題をフィルタリングします（例：「気候変動」、「エネルギーシステム」）

  • language (文字列、オプション): プログラミング言語で問題をフィルタリングします (例: 'JavaScript'、'Python')

  • keyword （文字列、オプション）：プロジェクトのキーワードで問題をフィルタリングします（例：「good first issue」、「help wanted」）

  • page （数値、オプション）：ページ番号（1から始まる）

  • per_page （数値、オプション）：ページあたりのレコード数（デフォルト：10）

  • sort (文字列、オプション): 並べ替えの基準となるフィールド ('created_at'、'updated_at'、'stars'、デフォルト: 'created_at')

  • order (文字列、オプション): 並べ替え順序 ('asc' または 'desc'、デフォルト: 'desc' (最新の順))

構成

デフォルトでは、サーバーはhttps://ost.ecosyste.ms/api/v1の ClimateTriage API に接続します。

Claude Desktopでの使用

これをclaude_desktop_config.jsonに追加します:

{
  "mcpServers": {
    "climate-triage": {
      "command": "npx",
      "args": ["-y", "git+https://github.com/Codeshark-NET/climate-triage-mcp.git"]
    }
  }
}

ライセンス

このMCPサーバーはMITライセンスに基づいてライセンスされています。つまり、MITライセンスの条件に従って、ソフトウェアを自由に使用、改変、配布することができます。

Available Tools

1 tool
search_climate_triage_issuesB

Searches for open source issues related to climate change, sustainability and more. Use this tool to find opportunities to contribute to projects addressing climate challenges, explore issues in specific programming languages, or discover projects in various sustainability categories. Returns information about issues including project details, descriptions, and links. Supports filtering, pagination, and sorting to help find relevant issues.

ParametersJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter issues by project category
keywordNoFilter issues by project keyword (e.g., 'bug', 'help wanted', 'enhancement')
languageNoFilter issues by programming language
orderNoSort order (asc or desc) (default: desc for most recent first)desc
pageNoPagination page number (starts at 1)
per_pageNoNumber of records per page (default: 10)
sortNoField to sort by (default: created_at). Use created_at for most recent issues first.created_at

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool 'returns information about issues including project details, descriptions, and links' and 'supports filtering, pagination, and sorting,' which adds useful context about output and capabilities. However, it doesn't cover critical aspects like rate limits, authentication needs, error handling, or data freshness, leaving gaps in behavioral understanding.

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?

The description is appropriately sized and front-loaded, starting with the core purpose and following with usage examples and capabilities. Each sentence adds value, with no redundant information. However, it could be slightly more streamlined by integrating the capabilities into the initial statement.

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?

Given the complexity (7 parameters, no annotations, no output schema), the description is moderately complete. It covers the purpose, output content, and supported features but lacks details on response format, error cases, or example outputs. Without an output schema, the agent must infer return values from the description alone, which is insufficient for full operational clarity.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds minimal parameter semantics beyond the schema, mentioning filtering, pagination, and sorting generically but not explaining specific parameter interactions or use cases. It doesn't compensate for schema gaps because there are none, but also doesn't enhance parameter understanding significantly.

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 searches for open source issues related to climate change and sustainability, specifying the resource (issues) and purpose (finding opportunities to contribute). It distinguishes the domain (climate/sustainability) but doesn't differentiate from siblings since none exist, making it clear but not fully optimized for sibling comparison.

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 description provides implied usage contexts ('to find opportunities to contribute,' 'explore issues,' 'discover projects') but lacks explicit guidance on when to use this tool versus alternatives. No exclusions or prerequisites are mentioned, leaving the agent to infer appropriate scenarios without clear boundaries.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedsearch_climate_triage_issues
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a clear, distinct purpose focused on searching for climate-related open source issues.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name follows a clear verb_noun pattern (search_climate_triage_issues), which would be consistent if more tools were added.

Tool Count2/5

A single tool is too few for a server named 'ClimateTriage MCP Server', which suggests a broader scope of climate-related operations. The tool only handles searching, leaving obvious gaps like creating, updating, or managing issues, making the server feel incomplete and under-scoped.

Completeness2/5

The server is severely incomplete for its implied domain of climate triage. It only provides search functionality, with no tools for creating, updating, deleting, or analyzing issues, which are essential for a full triage workflow. This will likely cause agent failures when trying to perform comprehensive climate-related tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • GitHub Issues MCP Server

    C-you-know
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to discover, filter, and triage GitHub issues across repositories, with tools for fetching issue details, listing issues by state/labels, and finding related pull requests.
    1
    MIT

  • github-issues-mcp

    nukathotipoojitha
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to list, search, and inspect issues on any public GitHub repository via natural language.
    MIT

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Codeshark-NET/climate-triage-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server