Skip to main content
Glama

Server Details

Whimbrel MedTech Analyst is your MedTech BD analyst on demand. Connect it to Claude, ChatGPT, Cursor or another AI app and ask about up-and-coming US medtech companies: who got funded this week through NIH and NSF grants and federal contracts, plus FDA clearances and Breakthrough marketing authorizations. Every line is linked to its source. Built for BD reps and small engineering firms researching companies they're interested in partnering with. Connect free: https://whimbrelresearch.com/connect/

Ownership verified
Status
Healthy
Uptime
57.0% over 22 days
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL

TDQS

A3.7/5.0

Scored across 21 tools

Disambiguation3/5

The signal-retrieval tools heavily overlap: latest_signals (14 days), find_signals (full corpus with the same filters), signal_of_the_day, weekly_pulse, who_got_funded, and space_scan all return subsets of the same buying-signal feed, distinguished mainly by window/aggregation rather than purpose. Similarly quick_company and company_timeline both return registry events for one company, and deep_record plus company_timeline's ask mode both yield account plans. Verbose descriptions help, but an agent can easily misselect among the signal tools.

Naming Consistency4/5

Names are uniformly snake_case and largely readable, mostly following a verb_noun or noun_phrase shape (find_signals, get_access, add_seat, watch_space, weekly_pulse). The verb prefixes are somewhat mixed (find_, get_, quick_, deep_, about_, who_got_funded), but the convention is consistent enough that no tool name is misleading.

Tool Count3/5

21 tools is on the heavy side for the apparent scope, and a meaningful chunk of that count comes from partially redundant signal views (latest_signals, find_signals, signal_of_the_day, weekly_pulse, space_scan) plus an entire billing/seat-management cluster. Each could be justified alone, but together they push the set past a tight, well-scoped surface.

Completeness4/5

Coverage of the medtech BD domain is broad: signals, company research, trials, suppliers, jobs, CRM export, watchlists, and account/billing lifecycle. Minor gaps exist (e.g. watch_space has save/diff but no remove, and there is no explicit company-update/delete for records), but core workflows are fully served.

Available Tools

20 tools
about_the_dataAbout this data
Read-onlyIdempotent
Inspect

How the archive is collected, dated, and windowed, what the feed excludes, and the licensing and attribution terms. Takes no inputs. Returns the methodology, the overview, and the published archive scale.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

accountThe rep's account
Idempotent
Inspect

The rep's own setup in one place. On first use it starts the profile build: ask_now is the first question (the firm's website) and say_now the message to send. Pass each answer with step set to ask_now.step (website reads the site and drafts the profile), or step with skip true, and it returns the next question, one at a time, then the read-back. Pass any profile field to change it (services, device_areas, customer_stage, territory, clients, competitors, skip_companies, accounts, and the rest). A change keeps the earlier answer, which the rep can put back from the Memory page; nothing is deleted. With nothing passed: the profile, who the rep sells to best, the team's seats, the account page for billing and invites, where the data comes from, and the Memory page. Returns set_up_now while the profile is not built yet.

ParametersJSON Schema
NameRequiredDescriptionDefault
roleNoThe rep's role.
skipNoWith step: the rep skipped that question or has none.
stepNoDuring the profile build: the ask_now.step being answered.
notesNo
proofNoKinds of projects delivered recently.
clientsNoThe firm's customers: kept out of lists, used as the picture of a good fit.
websiteNoThe firm's public website, to draft the profile from.
accountsNoCompanies the rep is working now.
servicesNoThe services that actually win the firm's work, in the rep's words.
firm_nameNo
territoryNo
buyer_rolesNo
competitorsNoCompeting firms: kept out of lists.
device_areasNo
certificationsNo
customer_stageNoearly-stage, growth-stage, established, or a mix.
device_classesNo
skip_companiesNo
check_space_watchWhat is new on a saved watchInspect

Returns the index signals that are new on a saved watch since it was saved or last checked, using the filters it was saved with, and marks them as seen so the next check starts from now.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe saved watch's name.
companyCompany rundown
Read-onlyIdempotent
Inspect

The rundown on one company from Whimbrel's list of US medical device companies and suppliers: whether it is on the list and why, what it makes, stage, location, FDA-registered facilities, every event on file (clearances, approvals, inspections, recalls, trials, grants, funding, news) with dates and source links, and the rep's own history with it (what they said, people they know there). Use it for "tell me about", "what's the history with" or "what do we know about" a company. A company not on the list says so, so the rep does not pitch a foreign importer or a drug company.

ParametersJSON Schema
NameRequiredDescriptionDefault
eventsNoHow many events to return, newest first (default 20, up to 60).
companyYesThe company's name as the rep said it.
crm_exportExport research as CRM import files
Read-onlyIdempotent
Inspect

One company's deep-research record as CRM import files. Pass company and format (hubspot or salesforce). Returns a companies/accounts CSV, a contacts CSV with the researched people and titles, a sourced research-notes document, and the import steps for that CRM. Requires an existing deep-research record and an active Whimbrel key.

ParametersJSON Schema
NameRequiredDescriptionDefault
formatYesWhich CRM the files should import into.
companyYesCompany name (must already have a deep-research record).
deep_recordQueue a full research recordInspect

A full research rundown on one company, for when the rep asks for one: current leadership and buying committee, company facts, contact routes, named partners, the evidence behind each, and known gaps. Pass company. Pass domain when asking for new research. Pass refresh to force a new run. Pass fact as email, clearance, or trial to return that stored fact only, without queueing a run. People already on the record are grouped by stored role. If the company has no record yet, or the newest record is more than a week old, this queues a fresh research run and returns the best file already stored, with a note on what is still filling. A record researched within the week is served as stored. Requires an active Whimbrel key.

ParametersJSON Schema
NameRequiredDescriptionDefault
factNoReturn this one stored fact and do not queue a research run. Omit it for the company file.
sinceNoISO date (YYYY-MM-DD) for the What changed section. Defaults to the last 90 days.
domainNoThe company's website domain (recommended when requesting new research; otherwise it is resolved, and the run fails honestly if it cannot be).
companyYesCompany name.
refreshNoForce a fresh research run even when a recent record exists. A record older than a week refreshes automatically without this.
findFind companies
Read-onlyIdempotent
Inspect

Finds US medical device companies by device, technology or space, a role being hired, a state or a date. One search across every kind of signal, answered as companies: a device, technology or space in plain words (about), and optionally a role being hired, a US state or a date. Looks at device trials, FDA device makers, filings and news, and hiring, folds them into one row per company with its evidence and sources, leaves out the rep's customers, competitors and passes, and ranks the rest for what was asked and what the rep's firm sells.

ParametersJSON Schema
NameRequiredDescriptionDefault
askNoOptional: the rep's request in their words, when it says more than about does (e.g. 'who just raised money and is still pre-clearance').
roleNoOptional: a role being hired, e.g. 'design transfer', 'sterilization'.
aboutNoA device, technology or space, e.g. 'balloon catheter', 'spinal implants', 'wearable glucose'.
limitNoMost companies to return (default 15, max 25).
sinceNoOptional ISO date; evidence on or after it.
stateNoOptional US state name.
looking_forNoOptional: limit to some kinds of evidence.
forgetForget a company or stop working it
DestructiveIdempotent
Inspect

Deletes what Whimbrel keeps for this rep about a company, when the rep asks: companies forgets what they said about it (its status, notes and history), stop_working takes it off the accounts they are working. The companies and their public records are not affected. People and the firm profile are edited on the rep's Memory page.

ParametersJSON Schema
NameRequiredDescriptionDefault
companiesNoCompanies whose status, notes and history to delete.
stop_workingNoCompanies to take off the rep's accounts.
get_accessGet a key for the paid toolsInspect

Returns Stripe Checkout links for Individual and Team. Both open with a one-month trial of the full paid product, then convert to paid. Individual is one person. Team is five or more people. Pass plan as individual or seat, or omit it to return both links. Pass quantity as the people on a seat checkout. A quantity below 5 is refused. No key is required. OAuth Subscribe on the sign-in page hands the token to the app with nothing to paste. These links are the display-key path for clients that do not use OAuth: open one, start the trial, then collect the key from the success page and send it as an Authorization Bearer header.

ParametersJSON Schema
NameRequiredDescriptionDefault
planNoWhich checkout to open. Omit to open both.
quantityNoPeople on a seat checkout. Below 5 is refused.
my_contactsThe rep's contacts
Read-onlyIdempotent
Inspect

The people the rep told Whimbrel they know, optionally at one company or matching a word, with role, how they met and when they last spoke.

ParametersJSON Schema
NameRequiredDescriptionDefault
searchNoA word in a name, company or role.
companyNo
my_listMy accounts
Idempotent
Inspect

The accounts the rep is working, on Whimbrel's list of US medical device companies: add companies, and see what changed at each since a date (default the last 7 days) with sources, what the rep last said about it and who they know there. Use it for "what changed at my accounts" or "track these". A name that is not a US device company says so. It does not remove companies.

ParametersJSON Schema
NameRequiredDescriptionDefault
addNoCompanies to start working.
sinceNoISO date; changes on or after it (default 7 days ago).
newsWhat's new in medtech
Read-onlyIdempotent
Inspect

What's new in US medtech, for news questions such as "any news in medtech", "what's new this week", "anything new in neuromodulation", "who got FDA clearance lately", "any recalls". The last days of sourced events at US medical device companies and their suppliers: FDA clearances and approvals, recalls and warning letters, device trials, funding and grants, press releases and hiring, one row per company with dates and source links, ranked for the rep's firm.

ParametersJSON Schema
NameRequiredDescriptionDefault
askNoThe rep's question in their words.
daysNoHow many days back (default 7, up to 90).
aboutNoOptional: a device, technology or space, e.g. 'neuromodulation'.
limitNoMost companies to return (default 15, max 25).
stateNoOptional US state name.
opening_line_factsFacts for an opening line
Idempotent
Inspect

What to write an opening line to one company from: what just happened there (a trial, a hire, an FDA decision, funding, news), each with its source, and from the rep's own profile the service it calls for, their closest past project, a certification the company asked for, and the angle when the company already uses another firm or resembles their clients. Also says how the company fits the rep (territory, stage) and who they already know there. Returns the facts, not the lines. Looking a company up here also counts it toward what Whimbrel learns the rep is drawn to, shown and removable on their Memory page.

ParametersJSON Schema
NameRequiredDescriptionDefault
companyYes
peopleWho to contact at a company
Idempotent
Inspect

Who to contact at one company, by role: R&D and engineering, quality, regulatory, clinical, supply chain and sourcing, operations and manufacturing, executive, business. Everyone the public record names there (the company's own site, award contacts, trial contacts and officials, filings), each with title, source, date and any published email or phone; work emails looked up for the top names when none is on record. People the rep already knows come first. Looking a company up here also counts it toward what Whimbrel learns the rep is drawn to, shown and removable on their Memory page.

ParametersJSON Schema
NameRequiredDescriptionDefault
roleNoOptional: the function to reach, in plain words (e.g. 'R&D', 'quality', 'sourcing').
limitNoMost people to return (default 25).
companyYes
rank_listRank a list of companies
Read-onlyIdempotent
Inspect

Orders a list of company names the rep pasted (a territory, an exhibitor list, a target list) for the rep's firm. Each company on Whimbrel's list of US medical device companies comes with its position, the fit, why now, its newest evidence with sources, what the rep last said about it and who they know there. Names not on the list come back apart, with why. Saves nothing.

ParametersJSON Schema
NameRequiredDescriptionDefault
companiesYesThe company names to rank, at most 60.
rememberRemember what the rep said
Idempotent
Inspect

Keeps what the rep says in passing: reached out, they replied, meeting booked, interested, a pass and why, not now and when, a customer, a competitor, went elsewhere, or a person they know at a company. It only adds and updates; a request to forget something returns to_forget, the companies it names, and deletes nothing. Takes the rep's words as said and the companies currently on screen so 'them' and 'the second one' resolve. Returns a few words saying what was kept, like "Got it, QT's a pass." Today's list and follow-ups use what is kept.

ParametersJSON Schema
NameRequiredDescriptionDefault
saidYesWhat the rep said, as they said it.
companies_on_screenNoCompanies shown in the conversation, in order, for 'them' and 'the second one'.
research_statusYour research requests
Read-onlyIdempotent
Inspect

Status of this account's queued, running, and finished research and onboarding requests. Pass request_id for one request, or omit it for the recent ten. On a Team plan, the reply includes seats claimed. Requires an active Whimbrel key.

ParametersJSON Schema
NameRequiredDescriptionDefault
request_idNoOne request to check; omit for your recent ten.
save_space_watchSave a space to watchA
Destructive
Inspect

Saves a named space from the Whimbrel signal index: the signals that match kind, since, new_award, phase, min_amount_usd and matching are stored under the name, for the calling account only. Saving the same name again replaces its saved signals with what matches now. Returns what was stored. Later replies open with one line when something new is on a saved watch; check_space_watch returns what is new.

ParametersJSON Schema
NameRequiredDescriptionDefault
kindNoonly this signal kind.
nameYesName for this space, e.g. 'neuromodulation startups'.
phaseNoNIH program phase.
sinceNoISO date (YYYY-MM-DD).
matchingNospace-separated terms matched against summary and abstract.
new_awardNoNIH first-year awards only.
min_amount_usdNostated amount at or above this.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, readOnly=false, idempotent=false, openWorld=false. The description adds real value beyond that: it discloses overwrite-on-reuse semantics, account scoping, that it returns what was stored, and that saved watches appear as a one-line notice in later replies. It does not describe permission requirements or limits on the number of saved spaces.

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?

Front-loads the save action and the stored-filter set, then handles replace semantics and read-back routing in short clauses. Dense but every sentence carries information; the final sentence about the opening line is a slight digression but still useful.

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?

No output schema exists, and the description covers the return at a high level ('Returns what was stored'). Combined with fully documented parameters and annotations covering the mutation profile, an agent has enough to call and interpret this correctly, though return shape details are thin.

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 every filter parameter is already documented in the schema. The description merely enumerates the filter names (kind, since, new_award, phase, min_amount_usd, matching) without adding format, semantics, or combination behavior beyond the schema. Baseline 3 applies.

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+resource: 'Saves a named space from the Whimbrel signal index', and immediately scopes it to the calling account. It also names the sibling check_space_watch as the way to read what is new, so an agent can distinguish save from read 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?

Explains the salient usage condition — re-saving a name replaces rather than duplicates — and routes the agent to check_space_watch for retrieving new items, and mentions the 'opening line' behavior that surfaces watches automatically. No explicit when-not-to-use guidance, so it falls 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.

todayToday's planInspect

The rep's plan for today, built from their profile and what they told Whimbrel: follow-ups that are due, what changed this week at the accounts they are working, and up to five new companies to reach out to (early signals such as trials not yet recruiting and the roles being hired), ranked for their firm, each with why now, the fit and who to contact. Leaves out customers, competitors, companies they passed on or already contacted, and anything shown in the last two weeks. Use it for "who should I reach out to", "plan my day" or "what's new for me".

ParametersJSON Schema
NameRequiredDescriptionDefault
sizeNoHow many new companies, 1 to 10 (default 5).
trade_showTrade show plan and follow-up
Idempotent
Inspect

Before a trade show: pass the show name, its dates and the exhibitor list (names the rep pasted or uploaded, or that you read off the show's exhibitor directory). Whimbrel checks each name against the archive, ranks the device companies for the rep's firm (must see, worth a stop) with what changed at each, and picks out the rep's own contacts, accounts, customers and competitors exhibiting. Long lists can go in several calls. After the show: pass met, the people and companies the rep met; each is remembered as met at the show, logged, and set to follow up in two days. With only a show name, returns the saved plan; with nothing, lists the rep's shows.

ParametersJSON Schema
NameRequiredDescriptionDefault
metNoAfter the show: who the rep met.
endsNoLast day.
showNoThe show, with its year, e.g. 'MD&M West 2027'.
startsNoFirst day, e.g. 2027-02-02.
exhibitorsNoExhibiting company names.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updates
    • Addedcheck_space_watch
    • Addedsave_space_watch
    • Removedwatch_space
  2. 6 tool updates
    • Changedmy_list3 fields changed
      • removedInput schema / properties / rank
        Removed value: -{
        -  "description": "A list of company names to rank for the rep's firm instead.",
        -  "items": {
        -    "type": "string"
        -  },
        -  "type": "array"
        -}
      • removedInput schema / properties / show
        Removed value: -{
        -  "description": "A trade show. With only name: its saved plan. With an empty name: the rep's saved shows.",
        -  "properties": {
        -    "ends": {
        -      "description": "Last day.",
        -      "type": "string"
        -    },
        -    "exhibitors": {
        -      "description": "Exhibiting company names.",
        -      "items": {
        -        "type": "string"
        -      },
        -      "type": "array"
        -    },
        -    "met": {
        -      "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"
        -          },
        -          "phone": {
        -            "type": "string"
        -          },
        -          "role": {
        -            "type": "string"
        -          }
        -        },
        -        "required": [
        -          "company"
        -        ],
        -        "type": "object"
        -      },
        -      "type": "array"
        -    },
        -    "name": {
        -      "description": "The show, with its year, e.g. 'MD&M West 2027'.",
        -      "type": "string"
        -    },
        -    "starts": {
        -      "description": "First day, e.g. 2027-02-02.",
        -      "type": "string"
        -    }
        -  },
        -  "type": "object"
        -}
      • removedInput schema / properties / watch
        Removed value: -{
        -  "description": "A named space to watch: save it, then diff it later for what is new.",
        -  "properties": {
        -    "action": {
        -      "description": "save stores what matches now; diff returns what is new since.",
        -      "enum": [
        -        "save",
        -        "diff"
        -      ],
        -      "type": "string"
        -    },
        -    "kind": {
        -      "description": "On save: only one kind of evidence, e.g. fda_clearance or trial_registration.",
        -      "type": "string"
        -    },
        -    "matching": {
        -      "description": "On save: words the evidence must match, e.g. 'neuromodulation'.",
        -      "type": "string"
        -    },
        -    "name": {
        -      "description": "Name for this space, e.g. 'neuromodulation startups'.",
        -      "type": "string"
        -    },
        -    "since": {
        -      "description": "On save: ISO date; evidence on or after it.",
        -      "type": "string"
        -    }
        -  },
        -  "required": [
        -    "name",
        -    "action"
        -  ],
        -  "type": "object"
        -}
    • Removedopeners
    • Addedopening_line_facts
    • Addedrank_list
    • Addedtrade_show
    • Addedwatch_space
  3. 1 tool update
    • Changedmy_list2 fields changed
      • addedInput schema / properties / show
        Added value: +{
        +  "description": "A trade show. With only name: its saved plan. With an empty name: the rep's saved shows.",
        +  "properties": {
        +    "ends": {
        +      "description": "Last day.",
        +      "type": "string"
        +    },
        +    "exhibitors": {
        +      "description": "Exhibiting company names.",
        +      "items": {
        +        "type": "string"
        +      },
        +      "type": "array"
        +    },
        +    "met": {
        +      "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"
        +          },
        +          "phone": {
        +            "type": "string"
        +          },
        +          "role": {
        +            "type": "string"
        +          }
        +        },
        +        "required": [
        +          "company"
        +        ],
        +        "type": "object"
        +      },
        +      "type": "array"
        +    },
        +    "name": {
        +      "description": "The show, with its year, e.g. 'MD&M West 2027'.",
        +      "type": "string"
        +    },
        +    "starts": {
        +      "description": "First day, e.g. 2027-02-02.",
        +      "type": "string"
        +    }
        +  },
        +  "type": "object"
        +}
      • addedInput schema / properties / watch
        Added value: +{
        +  "description": "A named space to watch: save it, then diff it later for what is new.",
        +  "properties": {
        +    "action": {
        +      "description": "save stores what matches now; diff returns what is new since.",
        +      "enum": [
        +        "save",
        +        "diff"
        +      ],
        +      "type": "string"
        +    },
        +    "kind": {
        +      "description": "On save: only one kind of evidence, e.g. fda_clearance or trial_registration.",
        +      "type": "string"
        +    },
        +    "matching": {
        +      "description": "On save: words the evidence must match, e.g. 'neuromodulation'.",
        +      "type": "string"
        +    },
        +    "name": {
        +      "description": "Name for this space, e.g. 'neuromodulation startups'.",
        +      "type": "string"
        +    },
        +    "since": {
        +      "description": "On save: ISO date; evidence on or after it.",
        +      "type": "string"
        +    }
        +  },
        +  "required": [
        +    "name",
        +    "action"
        +  ],
        +  "type": "object"
        +}
  4. 3 tool updates
    • Addedabout_the_data
    • Addedforget
    • Changedmy_list1 field changed
      • removedInput schema / properties / remove
        Removed value: -{
        -  "description": "Companies to stop working.",
        -  "items": {
        -    "type": "string"
        -  },
        -  "type": "array"
        -}
  5. 2 tool updates
    • Changedaccount2 fields changed
      • addedInput schema / properties / skip
        Added value: +{
        +  "description": "With step: the rep skipped that question or has none.",
        +  "type": "boolean"
        +}
      • addedInput schema / properties / step
        Added value: +{
        +  "description": "During the profile build: the ask_now.step being answered.",
        +  "type": "string"
        +}
    • Addednews
  6. 1 tool update
    • Addedcrm_export
  7. 21 tool updates
    • Removedabout_the_data
    • Removedbilling_portal
    • Removedcompany_timeline
    • Removedcrm_export
    • Removedfind_device_makers
    • Removedfind_signals
    • Removedfind_suppliers
    • Removedlatest_signals
    • Removedlog_outcome
    • Removedmy_profile
    • Removedquick_company
    • Removedrank_companies
    • Removedread_firm_website
    • Removedremember_contacts
    • Removedsave_profile
    • Removedsignal_of_the_day
    • Removedtrack
    • Removedtrade_show
    • Removedwatch_space
    • Removedweekly_pulse
    • Removedwho_got_funded
  8. 5 tool updates
    • Addedaccount
    • Addedcompany
    • Changedfind1 field changed
      • addedInput schema / properties / ask
        Added value: +{
        +  "description": "Optional: the rep's request in their words, when it says more than about does (e.g. 'who just raised money and is still pre-clearance').",
        +  "type": "string"
        +}
    • Addedmy_list
    • Addedremember
  9. 1 tool update
    • Changedsave_profile3 fields changed
      • addedInput schema / properties / buyer_roles
        Added value: +{
        +  "description": "Who the rep sells to inside a company, e.g. R&D and engineering, Quality, Regulatory, Clinical, Supply chain and sourcing, Operations and manufacturing, Executive.",
        +  "items": {
        +    "type": "string"
        +  },
        +  "type": "array"
        +}
      • changedInput schema / properties / customer_stage / description
        Previous value: -"early-stage, growth-stage, established, or a mix."New value: +"The company phase they sell to best: early-stage, growth-stage, established, or a mix."
      • addedInput schema / properties / device_classes
        Added value: +{
        +  "description": "FDA device classes the firm works on most.",
        +  "items": {
        +    "enum": [
        +      "Class I",
        +      "Class II",
        +      "Class III"
        +    ],
        +    "type": "string"
        +  },
        +  "type": "array"
        +}
  10. 2 tool updates
    • Addedopeners
    • Changedsave_profile3 fields changed
      • addedInput schema / properties / clients
        Added value: +{
        +  "description": "The firm's current clients. Kept out of prospect lists, watched for news (repeat and expansion work), and used as the picture of a good fit.",
        +  "items": {
        +    "type": "string"
        +  },
        +  "type": "array"
        +}
      • addedInput schema / properties / competitors
        Added value: +{
        +  "description": "Competing firms. Kept out of lists; their clients are displacement targets.",
        +  "items": {
        +    "type": "string"
        +  },
        +  "type": "array"
        +}
      • changedInput schema / properties / skip_companies / description
        Previous value: -"Current customers and competitors to leave out of lists."New value: +"Anything else to leave out of lists."

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources