Skip to main content
Glama

MedaRep

Company ownership changes

ownership_changes
Read-onlyIdempotent

Dated deals that changed who sells device products: acquisitions, mergers, carve-outs (Stryker's US spinal implants to VB Spine), spin-offs and renames, each in a sentence with what it means for a rep and its source. Filter by company (as asked, as it reported, or its owner now), procedure family (companies with FDA decisions in it) and since (YYYY-MM-DD). With a family and a place, each deal counts the surgeons there the company that changed hands engaged in the three years before it, naming the busiest the plan shows.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ownership_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipsNo5-digit ZIP codes forming a custom territory (as my_territories returns them).
metroNoMetro area by name ("Charlotte") or 5-digit CBSA code (16740). Can cross state lines.
sinceNoOnly deals closed since this day, YYYY-MM-DD.
stateNoTwo-letter state code, e.g. NC. Omit when giving a metro or counties.
citiesNoCities within the state, to narrow it.
familyNoProcedure family key from coverage (e.g. knee-arthroplasty, lumbar-fusion) or a plain name.
companyNoA company, e.g. NuVasive, Globus or Exactech.
countiesNo5-digit county FIPS codes forming a custom territory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: each result is a narrative sentence with a 'what it means for a rep' implication and a cited source, and the surgeon-engagement counting (three years pre-deal, busiest named) only fires under specific filter combinations. It does not discuss result volume or pagination, so not a 5.

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?

It is front-loaded with the core definition and packed into a single dense paragraph with little waste. But the final clause ('counts the surgeons there the company that changed hands engaged in the three years before it, naming the busiest the plan shows') is syntactically tangled and hard to parse on first read, which costs clarity. Tightening that sentence would raise the score.

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?

With 8 optional parameters, no output schema, and strong annotation coverage, the description does the work that matters: it says what a result looks like and what extra data appears under certain filter combinations. Territory-combination rules (e.g. omit state when giving a metro) live in the schema, so their absence here is acceptable. Minor gap: nothing on result limits or ordering by date.

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 baseline is 3. The description still adds meaning the schema lacks: `company` may match the name as asked, as the company reported it, or its current owner; `family` selects companies with FDA decisions in that family; and the phrase 'a family and a place' signals that the geographic parameters act as a combined territory input. That is real semantic lift over the field descriptions.

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 names a specific resource (dated ownership-change deals) and enumerates the event types it covers — acquisitions, mergers, carve-outs, spin-offs, renames — with a concrete example (Stryker's US spinal implants to VB Spine). It also states the return shape (one sentence per deal plus what it means for a rep and its source), which lets an agent distinguish it from profile-style siblings. It stops short of naming any sibling it replaces, so it lands at 4 rather than 5.

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?

It explains how to narrow results (by company, procedure family, and since-date) and describes an extra enrichment that only triggers when a family plus a place are supplied, which is useful invocation guidance. However, it never says when to prefer this over company_profile, changes_since, or territory_changes, and gives no exclusions or prerequisites. Usage is implied through the filter narrative rather than stated.

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