Skip to main content
Glama

List certification marks

list_marks
Read-onlyIdempotent

List the certification marks and rating systems NonToxicFinder tracks, with who owns each and what it covers. kind "rating" marks are scores, not certifications.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered without description help. The description adds value beyond them by stating what each entry contains (owner and coverage) and by clarifying that "rating"-kind marks are scores, not certifications — a semantic distinction an agent would otherwise misread. It stops short of describing ordering, completeness of the catalog, or overall count.

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?

Two short sentences, both earning their place, with the resource definition front-loaded and the rating-kind caveat trailing as a clarification. No preamble, no restatement of the tool name, no filler.

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

Completeness4/5

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

For a zero-parameter, read-only lister this is close to complete: the agent knows what is listed, what fields come back, and how the "rating" kind is interpreted. Since no output schema exists, the description carries the return-value burden alone, and it only sketches the fields rather than fully specifying the shape — a small remaining gap.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate at the argument level. The schema is empty with additionalProperties=false, consistent with the description's no-argument framing.

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 and resource ("List the certification marks and rating systems NonToxicFinder tracks") plus the attributes returned (owner, coverage). It also disambiguates the internal "rating" kind as scores rather than certifications, so the scope of the resource is unambiguous. No explicit contrast with siblings is offered, but the no-argument catalog behavior is distinct from get_article/get_product/search_products.

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?

Usage is only implied: the agent can infer this is the discovery/enumeration tool to consult before asking about a specific mark or product. There is no explicit "use this when..." statement and no exclusion pointing to an alternative (e.g., fetch details for a single mark). Adequate for a zero-parameter lister but not directive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources