carbonstop-mcp

Official

Overview Schema Source Related Servers Discussions Admin

accounts

Retrieve carbon footprint accounts (models) for a product by providing its ID. Filter by page, size, and status to manage emission models.

Instructions

List carbon footprint accounts (models) for a product.

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": {
      "productId": "<productId>"
    },
    "name": "accounts"
  }
}

Input Schema

Name	Required	Description
`productId`	Yes	Product ID (required)
`pageNum`	No	Page number (default 1)
`pageSize`	No	Page size (default 10)
`accountStatus`	No	Account status (default 3)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0May 28, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided. The description only says 'List', implying a read operation, but does not disclose pagination behavior, default status, return format, or any side effects. For a tool with no annotations, more behavioral detail is needed.

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 a single concise sentence with no waste. However, it could include more useful information without becoming overly long.

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

Completeness2/5

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

Given 4 parameters and no output schema, the description is too minimal. It does not explain return values, pagination details, or the meaning of account status. The tool's complexity is low but the description falls short.

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?

Schema coverage is 100% with descriptions for all 4 parameters, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions, which are self-explanatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (list) and the resource (carbon footprint accounts/models for a product). It is specific and distinguishes from siblings like 'account_view' which likely focuses on a single account.

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 on when to use this tool versus alternatives (e.g., 'account_view' for individual account details) or when not to use it. Lacks context on prerequisites or filters.

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

Deploy Server