Skip to main content
Glama
Sign In
carbonstop-mcp

carbonstop-mcp

Official
by carbonstop-hub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

products

List carbon footprint products with pagination, status filter, and product name search.

Instructions

List carbon footprint products with pagination and filtering.

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

Input Schema

NameRequiredDescriptionDefault
pageNumNoPage number (default 1)
pageSizeNoPage size (default 12)
statusNoStatus filter (default 2)
searchNoSearch by product name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It indicates a list operation with pagination and filtering, implying it is read-only, but does not mention any side effects, authentication needs, rate limits, or other behaviors beyond what the schema conveys.

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 description is a single, front-loaded sentence of 7 words with no unnecessary information. Every word is meaningful, making it efficient and easy to parse.

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 the lack of output schema, the description should clarify return format or fields, but it does not. It only covers the input features, leaving the output ambiguous. For a list tool with 4 parameters and no annotations, this is insufficient.

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?

All four parameters have descriptions in the input schema (100% coverage), so the description adds no extra meaning. It summarizes the parameters as 'pagination and filtering' but does not enhance understanding beyond the schema.

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 uses a specific verb 'list' and specifies the resource 'carbon footprint products', clearly indicating the tool's function. It also mentions pagination and filtering, distinguishing it from siblings like 'product_info' which likely provides details on a single product.

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 implies usage for listing products with filters, but does not explicitly state when to use this tool over alternatives such as 'product_info' or 'search_factors'. No guidance on prerequisites or exclusions is provided.

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