Skip to main content
Glama

SourceGeek

Read shortlist feedback

read_shortlist_feedback
Read-only

Read review feedback captured on a shortlist or candidate sheet artifact. Returns each reviewer's decision (advance/maybe/reject), structured signals (e.g. too_junior, wrong_domain, similar_profile_wanted), and free-text comments, grouped per candidate. Use it to summarize hiring-team calibration and propose role-plan updates.

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

Input Schema

NameRequiredDescriptionDefault
artifactIdNoThe shortlist or sheet artifact id to read feedback for. If omitted, uses the latest artifact in the thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that by disclosing the shape of the result — per-reviewer decisions, named structured signals, and free-text comments grouped per candidate. It does not discuss permissions, empty/missing feedback, or artifact fallback behavior, which is the main remaining gap.

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 sentences, each doing distinct work: what is read, what comes back, and what to use it for. Purpose is front-loaded and the illustrative signal names add precision without bloat.

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?

No output schema exists, so the description carries the burden of describing returns — and it does so concretely. Combined with annotations covering the safety profile and a fully documented single parameter, an agent has everything needed to select and invoke this 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?

With one optional parameter at 100% schema description coverage, the schema already explains artifactId and its default-to-latest-thread-artifact behavior. The description only echoes the artifact concept ("shortlist or candidate sheet artifact") without adding format, ID syntax, or fallback nuance, 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?

States a specific verb and resource: read review feedback captured on a shortlist or candidate sheet artifact. The sentence on return contents (decisions, structured signals, free-text comments grouped per candidate) makes it clearly distinct from a generic read_artifact. It stops short of explicitly naming which sibling to use instead, so it is clear but not fully sibling-differentiated.

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?

"Use it to summarize hiring-team calibration and propose role-plan updates" gives a concrete usage context. There is no when-not guidance and no alternative tool named (e.g. read_artifact for raw sheet contents), but the intended scenario is unambiguous.

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