Skip to main content
Glama

SourceGeek

Create shortlist

create_shortlist

Create an evidence-backed markdown shortlist from a scored candidate sheet. The tool ranks candidates by score, writes table and dossier sections, labels confirmed evidence, inferred fit, missing information, risks, next actions, and outreach angles, then saves the shortlist as a text artifact. It returns the shortlisted candidates with their rank, score and main reason.

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_shortlist"
  }
}

Input Schema

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

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?

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and the description adds real substance on top: it ranks by score, emits specific section types (table, dossier, confirmed evidence, inferred fit, missing information, risks, next actions, outreach angles), saves a text artifact, and returns rank/score/main reason. It does not state whether an existing artifact is overwritten or where the artifact lands, which is the main remaining behavioral unknown for a write tool.

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, front-loaded with the core action and input, then what gets produced, then what is returned. No filler, no restated title, and the final sentence covers return values that no output schema provides.

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 3-parameter artifact-generating tool with no output schema, the description covers the input prerequisite, the generation behavior, artifact persistence, and the return shape. Only minor gaps remain: overwrite/duplication behavior on repeated calls and failure modes when the source sheet is unscored.

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 all three parameters are already self-documenting; baseline is 3. The description does add a little meaning by specifying that artifactId must be a *scored* sheet and that ranking/limit selection is score-driven, but it never mentions the title parameter or the default/maximum of limit, so it does not meaningfully exceed 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 gives a specific verb + resource + source: it creates an evidence-backed markdown shortlist from a scored candidate sheet, ranks by score, writes table/dossier sections, and saves a text artifact. That is far more than a restatement of the name. It stops short of differentiating itself from the sibling create_rediscovery_shortlist, so an agent cannot tell from the text alone which shortlist tool fits a given case.

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?

Usage is implied rather than stated: the input must be a 'scored candidate sheet', which tells the agent the prerequisite artifact type. There is no explicit when-to-use/when-not guidance and no pointer to create_rediscovery_shortlist or any alternative, leaving the choice between shortlist tools to inference.

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