Skip to main content
Glama

Dictionary of Applied Machine Learning

List every term

list_all_terms
Read-onlyIdempotent

List every term of the Dictionary of Applied Machine Learning, one per line, as its display name followed by its key. Takes no arguments. Use it to find the key for a term before calling one of the tools that takes one.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered elsewhere. The description adds two useful behavioral facts beyond that: it takes no arguments and the result is a flat name-plus-key line format. It says nothing about result size or whether the list is exhaustive across the dictionary's full contents.

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?

Three short sentences, each doing distinct work: what is returned, the exact line format, and when to reach for it. Nothing is padded and the key detail, the output format, appears early.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and discharges it by specifying the per-line format. For a zero-parameter list tool with full annotation coverage, an agent has everything needed to call it correctly.

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?

There are zero parameters, which sets the baseline at 4. The explicit note that it "takes no arguments" confirms the empty schema rather than adding new meaning, which is acceptable at this baseline.

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 verb and resource ("List every term of the Dictionary of Applied Machine Learning") and even specifies the output shape: one term per line as display name followed by key. It implicitly separates itself from search_terms by emphasizing listing everything, but it never names the sibling it differs from, so differentiation is left to inference.

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 gives a clear use case: find the key for a term before calling a tool that requires one. That is a genuine routing instruction rather than a restatement of the name. It stops short of exclusions, such as telling the agent to use search_terms or lookup_term when it already knows the term name.

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.