Skip to main content
Glama

Whimbrel: Medtech Research

by com.whimbrelresearch
OverviewDiscussionsAdmin

Rank a list of companies

rank_list

Orders a list of company names the rep pasted (a territory, an exhibitor list, a target list) for the rep's firm. Each company Whimbrel covers comes with its position, the fit, why now, its newest evidence with sources, and the rep's status for it when they set one (a client, or not a fit). Names Whimbrel does not cover come back apart, with why. With a name ("rank these and save them as MD&M West 2027"), it also saves the ranked set under that name, the same set the Whimbrel app shows under Rankings; without one it saves nothing.

Input Schema

NameRequiredDescriptionDefault
nameNoOptional: save the ranked set under this name (Rankings in the app).
companiesYesThe company names to rank, at most 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Optional: save the ranked set under this name (Rankings in the app).",
+  "type": "string"
+}
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only mark this as a non-read-only, non-destructive, non-idempotent call; the description adds the crucial conditional side effect (a name saves the set under Rankings, no name saves nothing) plus the shape of the result, including uncovered names returned separately with reasons. That is real context the annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the prose is chatty, with parenthetical examples and a repeated restatement of the save-versus-no-save behavior that could be one clause. Each sentence carries information, yet the phrasing is longer than needed.

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?

There is no output schema, and the description compensates by enumerating the returned fields (position, fit, why now, newest evidence with sources, rep status) and the handling of uncovered names. An agent knows what it will get back and what side effect occurs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a 3 would be the floor, but the description goes further by explaining that 'name' is what triggers persistence and ties it to the app's Rankings view. It adds no detail on the 60-name cap since the schema already states it.

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 concrete verb and resource (orders a pasted list of company names) and describes what the ordering consists of. It implicitly separates itself from list_ranked_sets/open_ranked_set by explaining that ranking produces a set that may then be saved, but it never names a sibling as the alternative.

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?

It gives clear triggering context (a rep pasted a territory, exhibitor list, or target list) and spells out the branch between passing a name versus omitting one. It stops short of saying when to use list_ranked_sets/open_ranked_set instead or what happens on resubmission.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Whimbrel: Medtech Research toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources