Skip to main content
Glama

Define an AI concept

define_term
Read-onlyIdempotent

A plain-language definition of an AI product concept (tokens, temperature, RAG, embeddings, LLM-as-judge, prompt injection…), with the lessons that teach it.

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": {
      "term": "<term>"
    },
    "name": "define_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe AI term to define, e.g. 'RAG', 'temperature' or 'prompt caching'

Output Schema

NameRequiredDescriptionDefault
textYesThe answer in markdown, as shown to the user; for the guides, instructions to follow with the user's text
linksYesThe AI PM Lab pages the answer links to, where each idea can be tried hands-on

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, openWorldHint=false and destructiveHint=false, so safety is fully covered and the description correctly does not restate it. The one extra it adds is that results carry associated teaching lessons, which is useful behavior context beyond the annotations. It says nothing about coverage, fallback behavior for unknown terms, or match strictness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the core noun and scope, with examples bracketed at the end. It is a noun phrase rather than a verb phrase, a minor stylistic weakness, but nothing is wasted.

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 an output schema, rich annotations, and a single fully documented parameter, the description need only convey scope and that the response includes teaching lessons, which it does. Nothing an agent needs in order to call this correctly is missing.

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 description coverage is 100% and the single 'term' parameter is documented with examples in the schema itself. The description's examples mirror rather than extend the schema, so 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?

The description names the resource precisely: a plain-language definition of an AI product concept, and adds that it returns teaching lessons. The parenthetical examples (tokens, temperature, RAG, embeddings, LLM-as-judge, prompt injection) sharply bound the scope. It stops short of differentiating from siblings such as search_lessons or get_lesson, which are the nearest overlaps.

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?

Use is implied (look up a term, get a definition), but there is no explicit when-to-use or when-not-to-use guidance, and no pointer to get_lesson / search_lessons for deeper follow-up. Nothing is misleading, but the agent must infer the routing.

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