Skip to main content
Glama

get_criteria

Read-onlyIdempotent

The six criteria every listing is marked against, with definitions and the support values (native = Built in, pattern = Documented pattern, none = Not claimed).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so readability and safety are covered. The description adds modestly useful context by revealing that the result is a fixed set of six criteria and by enumerating the three support values (native/pattern/none), which tells the agent what values to expect. It does not say whether the set is static or configurable, nor describe the shape of each entry.

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?

A single sentence with the resource and its contents front-loaded and zero filler. The parenthetical enum gloss is dense but earns its place by pre-empting ambiguity about the support values.

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 no-parameter lookup with no output schema, the description adequately conveys what the caller gets back: six criteria with definitions and support-value semantics. Adding a note on return shape or on how these criteria feed pre_check would close the 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 schema imposes nothing to explain. The description correctly adds no parameter detail and instead spends its words on the returned content, which is the right allocation.

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 resource (the six criteria every listing is marked against) and states exactly what each entry contains: a definition plus support values. It is clear what the tool returns, though it never differentiates itself from siblings like pre_check or compare_tools, which presumably consume these same criteria.

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 statement of when to call this versus alternatives, and no prerequisites or exclusions are named. A reader can infer it is reference data needed to interpret listing evaluations, but that inference is left entirely to the agent.

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