Skip to main content
Glama

Whimbrel: Medtech Research

by com.whimbrelresearch
OverviewDiscussionsAdmin

Trade show booths to visit

trade_show
Read-onlyIdempotent

Ranks a trade show's exhibitor list for the rep's firm: pass the exhibitor names the rep pasted or uploaded, or that you read off the show's exhibitor directory. Whimbrel checks each name against the archive and returns the must-see booths and the ones worth a stop, each with why it fits the firm and what changed there, with sources. The rep's clients and the companies that are not a fit are left out. Saves nothing. A list longer than 200 names goes in several calls. Whimbrel does not hold any show's exhibitor list: without one, say "Whimbrel does not have this show's exhibitors; paste the list and I will rank it."

Input Schema

NameRequiredDescriptionDefault
showNoOptional: the show, with its year, e.g. 'MD&M West 2027'.
exhibitorsYesExhibiting company names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / ends
      Removed value: -{
-  "description": "Last day.",
-  "type": "string"
-}
    • removedInput schema / properties / met
      Removed value: -{
-  "description": "After the show: who the rep met.",
-  "items": {
-    "properties": {
-      "company": {
-        "type": "string"
-      },
-      "email": {
-        "type": "string"
-      },
-      "follow_up": {
-        "description": "When to follow up (default two days from now).",
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "note": {
-        "description": "What they talked about, in the rep's words.",
-        "type": "string"
-      },
-      "outcome": {
-        "description": "Default contacted.",
-        "enum": [
-          "contacted",
-          "replied",
-          "meeting",
-          "interested",
-          "not_fit",
-          "not_now",
-          "customer",
-          "competitor",
-          "lost"
-        ],
-        "type": "string"
-      },
-      "phone": {
-        "type": "string"
-      },
-      "role": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "company"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • changedInput schema / properties / show / description
      Previous value: -"The show, with its year, e.g. 'MD&M West 2027'."New value: +"Optional: the show, with its year, e.g. 'MD&M West 2027'."
    • removedInput schema / properties / starts
      Removed value: -{
-  "description": "First day, e.g. 2027-02-02.",
-  "type": "string"
-}
    • addedInput schema / required
      Added value: +[
+  "exhibitors"
+]
  2. Added
  3. Removed
  4. Added

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it returns must-see and worth-a-stop booths with fit rationale, change notes, and sources; excludes clients and non-fit companies; saves nothing; and explicitly says Whimbrel does not hold any show's exhibitor list. This is unusually complete for an agent deciding whether and how to call it.

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

Conciseness4/5

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

The description is front-loaded with the ranking action and return categories, and every sentence carries relevant instructions or constraints. It is somewhat long but mostly earns its length through operational detail.

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?

With no output schema, the description still explains the return structure (must-see vs. worth-a-stop booths with reasons, changes, and sources), the exclusion behavior, the no-save behavior, and the fallback when no exhibitor list exists. It is complete enough for an agent to invoke correctly.

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 the schema already documents exhibitors and show. The description still adds useful semantics: exhibitors may come from pasted, uploaded, or directory-read names, and lists over 200 should be split across multiple calls.

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: it ranks a trade show's exhibitor list for the rep's firm and returns must-see booths with reasons. It does not mention the sibling tool rank_list, so it falls short of full sibling differentiation.

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 operational guidance: pass exhibitor names the rep pasted, uploaded, or read from the directory, and split lists longer than 200 names across calls. It also tells the agent what to do when no exhibitor list is available, though it does not compare itself directly to alternatives like rank_list.

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