Skip to main content
Glama
@climeqai/mcp-server

@climeqai/mcp-server

Official
by climeqai

climeq_list_private_factors

Read-onlyIdempotent

Retrieve supplier-specific EPDs and primary emission factors owned by your organization, with pagination, to support accurate Scope 3 and product carbon footprint calculations.

Instructions

List supplier-specific EPD or primary emission factors owned by the authenticated organization.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
pageSizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful scoping context (results are limited to factors owned by the caller's organization), but says nothing about pagination, result size, or whether an empty list is a normal outcome.

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?

A single front-loaded sentence with no filler; the enumerative scope is stated immediately. It is efficient, though slightly dense with qualifiers ('supplier-specific', 'primary') that could be resolved more plainly.

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?

For a simple two-parameter read-only list tool with full annotation coverage and no output schema, the core intent is conveyed. However, with no output schema and zero parameter descriptions, the agent is left without any sense of what is returned per item or how to page through large result sets.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden of explaining page/pageSize, and it says nothing about them. The schema does supply defaults and bounds (page default 1, pageSize default 20, max 100), which mitigates the gap somewhat, but no meaning about paging behavior is added by the text.

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 names a specific verb ('List') and a specific resource ('supplier-specific EPD or primary emission factors owned by the authenticated organization'), which is enough to separate it from climeq_create_private_factor and climeq_search_factors. It does not explicitly state the contrast with those siblings, so it stops short of a 5.

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 explicit when-to-use guidance: it never says whether to prefer this over climeq_search_factors for private factors or when creating vs listing. The only implied guidance is the ownership scope ('authenticated organization'), which an agent could infer is the unfiltered enumeration of private factors.

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