Skip to main content
Glama
Sign In
WISEPIM Commerce Reference

WISEPIM Commerce Reference

by lldiegon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

check_green_claims

Read-onlyIdempotent

Flags environmental claims in product copy for human review under Directive (EU) 2024/825 using phrase matching, not evidence or legal compliance assessment.

Instructions

Flag environmental claims in product copy for human review under Directive (EU) 2024/825. Phrase matching cannot assess evidence or establish legal compliance.

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": {
      "text": "<text>"
    },
    "name": "check_green_claims"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, idempotent operation. The description adds valuable behavioral context beyond annotations: the tool is a phrase-matching aid for human review and explicitly cannot assess evidence or determine legal compliance. It omits what the flagged output actually contains, which is a gap but not a contradiction.

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 definition is two tightly written sentences: the first front-loads purpose and scope, the second immediately qualifies the limitation. No wording is wasted.

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 that there is no output schema and 0% parameter description coverage, the description should explain what a 'flag' returns (e.g., list of matches, offsets, categories) and how language and text length are handled. It leaves these operational details absent, making it incomplete for correct invocation.

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 should compensate, but it says nothing about the 'text' or 'language' parameters. At best, 'product copy' implies the text parameter, but the language parameter (with its four enum values) and its default are entirely unaddressed.

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 gives a specific verb ('Flag') and resource ('environmental claims in product copy') and cites the relevant regulation. It does not explicitly differentiate from its siblings lookup_hs_heading or marketplace_requirements, but the domain is distinct enough for an agent to understand its role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the use case ('for human review') and an important exclusion ('cannot assess evidence or establish legal compliance'). However, it does not name alternative tools or explain when to prefer a sibling over this one, leaving some routing ambiguity.

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