Skip to main content
Glama

list_biases

Read-onlyIdempotent

List the 22-bias catalogue, optionally filtered by family.

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_biases"
  }
}

Input Schema

NameRequiredDescriptionDefault
familyNoOptional. Only the biases in this family; omit for all 22.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / family / description
      Added value: +"Optional. Only the biases in this family; omit for all 22."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the catalogue size (22) and the family-filtering behavior, without saying what a returned entry looks like (name, id, summary) — context that would help the agent chain into get_bias.

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 10-word sentence that front-loads the verb and resource and appends the modifier. Nothing is redundant or padded.

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 one-optional-parameter read tool with rich annotations and no output schema, the definition covers purpose and filtering adequately. The only shortfall is not indicating the shape or fields of the returned catalogue entries, which would ease follow-up calls to get_bias.

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% and the family parameter already carries an enum plus the text 'Only the biases in this family; omit for all 22.' The description's 'optionally filtered by family' merely restates this, adding no new semantics, so the baseline 3 applies.

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?

States a specific verb (List) and resource (the 22-bias catalogue) with scope (optionally filtered by family). The word 'catalogue' differentiates it from get_bias, which fetches a single entry, but the description never names that sibling explicitly.

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 phrase 'optionally filtered by family' implicitly tells the agent this is a browse-all-or-subset tool, and the schema note 'omit for all 22' reinforces the default. There is no explicit when-to-use versus get_bias or analyze_decision, so an agent must infer that it should call this first to discover bias names.

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.