Skip to main content
Glama

Whimbrel MedTech Analyst

by com.whimbrelresearch
OverviewDiscussionsAdmin

Save a space to watch

save_space_watch
Destructive

Saves a find search under a name, for the calling account only: a device, technology or space (about) or a role being hired (role), with an optional US state and kinds of evidence. Returns the device companies on Whimbrel's list it matches now, ranked as find ranks them. Saving the same name again replaces the search. Later replies open with one line when the watch has new evidence; check_space_watch returns it.

Input Schema

NameRequiredDescriptionDefault
nameYesName for this watch, e.g. 'neuromodulation startups'.
roleNoOptional: a role being hired, e.g. 'design transfer'.
aboutNoA device, technology or space, e.g. 'neuromodulation'.
stateNoOptional US state name.
looking_forNoOptional: limit to some kinds of evidence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / about
      Added value: +{
+  "description": "A device, technology or space, e.g. 'neuromodulation'.",
+  "type": "string"
+}
    • removedInput schema / properties / kind
      Removed value: -{
-  "description": "only this signal kind.",
-  "enum": [
-    "nih_award",
-    "nsf_award",
-    "federal_contract",
-    "sbir_award",
-    "fda_clearance",
-    "fda_pma",
-    "fda_denovo",
-    "fda_breakthrough_auth",
-    "fda_hde",
-    "fda_listing",
-    "fda_recall",
-    "fda_warning_letter",
-    "fda_import_alert",
-    "fda_483",
-    "fda_pma_supplement",
-    "fda_pma_original",
-    "trial_registration",
-    "funding_filing",
-    "company_news"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / looking_for
      Added value: +{
+  "description": "Optional: limit to some kinds of evidence.",
+  "items": {
+    "enum": [
+      "trials",
+      "device_makers",
+      "filings_and_news",
+      "hiring"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / matching
      Removed value: -{
-  "description": "space-separated terms matched against summary and abstract.",
-  "type": "string"
-}
    • removedInput schema / properties / min_amount_usd
      Removed value: -{
-  "description": "stated amount at or above this.",
-  "type": "number"
-}
    • changedInput schema / properties / name / description
      Previous value: -"Name for this space, e.g. 'neuromodulation startups'."New value: +"Name for this watch, e.g. 'neuromodulation startups'."
    • removedInput schema / properties / new_award
      Removed value: -{
-  "description": "NIH first-year awards only.",
-  "type": "boolean"
-}
    • removedInput schema / properties / phase
      Removed value: -{
-  "description": "NIH program phase.",
-  "enum": [
-    "SBIR Phase I",
-    "SBIR Phase II",
-    "STTR Phase I",
-    "STTR Phase II"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / role
      Added value: +{
+  "description": "Optional: a role being hired, e.g. 'design transfer'.",
+  "type": "string"
+}
    • removedInput schema / properties / since
      Removed value: -{
-  "description": "ISO date (YYYY-MM-DD).",
-  "type": "string"
-}
    • addedInput schema / properties / state
      Added value: +{
+  "description": "Optional US state name.",
+  "type": "string"
+}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=false; the description is consistent, disclosing that 'Saving the same name again replaces the search' and that the write is scoped to the calling account. It could be more explicit that the prior watch is overwritten/lost, but it adds real behavioral context (ranked result set, later reply behavior) on top of the annotations.

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 core action and replacement semantics are front-loaded, and sentences are dense with no filler. The trailing sentence about later replies and check_space_watch is slightly tangential to invoking this tool but earns its place by explaining the watch lifecycle.

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 mutation tool with no output schema, the description covers all the key concerns: account scoping, overwrite behavior on duplicate name, and what the immediate response contains (matching device companies, ranked as find ranks them). It is complete enough to call correctly.

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 coverage is 100%, so the schema already documents all five parameters and their examples. The prose largely restates those fields ('a device, technology or space (about) or a role being hired (role)'), adding only minor relational framing between about/role, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Saves a find search under a name, for the calling account only.' It also names the two modes (about / role) and the retrieval sibling check_space_watch, so an agent can distinguish it from check_space_watch without opening either schema.

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?

The description gives clear context for when this is used (to persist a search that later surfaces new evidence) and routes the agent to check_space_watch for retrieval. It does not state exclusions, e.g. when to prefer find or remember instead, so it stops short of a 5.

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

All Whimbrel MedTech Analyst 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