Skip to main content
Glama

SourceGeek

Create rediscovery shortlist

create_rediscovery_shortlist

Create a markdown shortlist from a talent rediscovery sheet with source context, prior status, match rationale, and recommended re-engagement actions.

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": {
      "artifactId": "<artifactId>"
    },
    "name": "create_rediscovery_shortlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of candidates to include.
titleNoOptional title for the generated shortlist text artifact.
artifactIdYesThe rediscovery sheet artifact id to shortlist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description adds useful behavior detail by naming the markdown output and the sections it will include, but it does not say whether a new artifact is always created, how existing artifacts are handled, or what happens with an invalid artifactId.

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?

The description is a single front-loaded sentence with no filler, and every listed element contributes to understanding the generated shortlist.

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?

There is no output schema, and the description compensates by explaining the output format and contents of the generated shortlist. It remains incomplete on when to choose this tool over sibling creators and on the behavioral effects of the optional limit and title parameters.

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 artifactId, limit, and title are already documented in the schema. The description adds only light context that the artifact is a talent rediscovery sheet, which the schema already states, and gives no additional meaning for limit or title beyond the schema.

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 states a specific verb and resource: creating a markdown shortlist from a talent rediscovery sheet, and lists the sections it will contain. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as create_shortlist or create_sheet.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool, when not to use it, prerequisites, or alternatives. The only implied usage is that a talent rediscovery sheet must exist, and sibling creators are not referenced.

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