Skip to main content
Glama

QueryMind

Correct a personal definition

define

Propose a business definition for this user's questions only. First send term and definition, then show the preview to the user. Send confirm_token only after their explicit confirmation. Use undo_def_id to undo or list=true to list definitions.

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

Input Schema

NameRequiredDescriptionDefault
listNoSet true to list personal definitions.
termNoBusiness term to define.
previewNoDefaults to true.
definitionNoThe user's intended business definition.
undo_def_idNoID of a personal definition to undo.
confirm_tokenNoToken from a preview explicitly approved by the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations mark this as non-read-only, non-idempotent, and non-destructive, and the description adds genuinely new behavioral content: a preview gate that requires explicit user approval before confirm_token is sent. That is useful safety context beyond the annotations. It does not explain what happens on an invalid or stale token or whether an undo is permanent.

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?

Four short sentences that front-load the purpose and then walk through the workflow in execution order, with no filler. The phrase "for this user's questions only" is the one piece of wording that does not earn its place because it is ambiguous rather than informative.

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

Completeness3/5

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

This is a six-parameter, multi-mode tool with no output schema and no idempotency, so the description carries real weight. It covers the happy-path flow but leaves out what preview returns, what success looks like after confirmation, and how the modes relate to sibling tools, which is a notable gap for a stateful mutation tool.

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%, so the baseline is 3. The description adds limited extra meaning by imposing an ordering between term/definition, preview, and confirm_token, but most of what it says (list=true lists, undo_def_id undoes) only restates the existing schema descriptions.

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 ("Propose a business definition") and enumerates the tool's modes: define, preview/confirm, undo (undo_def_id), and list (list=true). The odd qualifier "for this user's questions only" blurs the scope, and nothing distinguishes it from siblings such as ask, clarify, or explain, so an agent cannot fully rule out alternatives from the text alone.

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?

It gives a clear internal sequencing rule (term and definition first, then preview, then confirm_token only after explicit user confirmation) and names the undo/list modes. However, it never says when to use define rather than ask/clarify/explain, and it omits prerequisites for correcting an existing definition versus creating a new one.

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