Skip to main content
Glama

QueryMind

Review definition candidates

review

List or propose approval/rejection of onboarding candidates (table labels, joins, code dictionaries). An administrator must confirm changes through a secure reauthentication link.

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

Input Schema

NameRequiredDescriptionDefault
actionNolist, approve or dismiss.
candidate_idsNoCandidate IDs returned by list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description discloses a genuinely non-obvious behavioral trait beyond the annotations: decisions are only proposals and an administrator must confirm via a secure reauthentication link, which explains why readOnlyHint=false and idempotentHint=false. This is the key operational context an agent needs. It stops short of saying what happens to an unconfirmed proposal or whether proposals expire.

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?

Two sentences, zero filler: the capability is stated first and the administrative-confirmation constraint second. Every clause carries information an agent would otherwise have to guess.

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 zero-required-parameter tool with no output schema, the description covers what is acted on and the two-step confirmation model, which is the main thing an agent could get wrong. Minor gaps remain around list output shape and what a 'propose' actually returns, but the core is complete.

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 both parameters are already documented, including the enum values and that candidate_ids come from list. The description reinforces that the two actions are approval and rejection and names the candidate types, but adds no syntax or behavioral detail (e.g., whether candidate_ids is required for approve/dismiss) beyond the schema. 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 opens with a specific verb pair and resource: 'List or propose approval/rejection of onboarding candidates', and clarifies the domain with examples (table labels, joins, code dictionaries). It does not explicitly differentiate itself from siblings such as onboarding_status or clarify, but the verb+resource is unambiguous enough to identify the tool.

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 'List or propose approval/rejection' implicitly maps to the action enum, so an agent can infer that list is for discovery and approve/dismiss for decisions. However, there is no explicit when-not guidance, no mention of when to prefer onboarding_status or clarify, and no statement that candidate_ids should be omitted when listing.

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