Skip to main content
Glama

US clinician data from Doximity's public directory

b2b_doximity
Read-only

US clinician data from Doximity's public directory. By profile (slug or doximity.com/pub URL): name, credentials, specialty, practice address with coordinates, phone, fax, education and training, board certifications, awards and hospital affiliations when listed. By location (state or state/city, e.g. north-carolina/raleigh): an alphabetical page of 50 clinicians with name, credentials and slug, plus a next-page cursor. Related tools on this server, for a different need: b2b_manta when you need Manta US small-business directory search by keyword; b2b_bbb when you need Better Business Bureau search: finds businesses by name. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "b2b_doximity"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoLocation mode: cursor from a previous page (nextAfter)
profileNoProfile slug (e.g. jane-smith-md) or https://www.doximity.com/pub/<slug> URL
locationNoDirectory location: state or state/city slug, e.g. north-carolina/raleigh

Output Schema

NameRequiredDescriptionDefault
faxNo
urlNo
zipNo
cityNo
nameNo
slugNo
phoneNo
stateNo
addressNo
jobTitleNo
latitudeNo
sectionsNo
checkedAtNo
longitudeNo
specialtyNo
credentialsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds valuable non-annotation context: explicit pricing ($0.002 USDC per successful call via x402 on Base, Solana or Arc) and the fact that failed calls are not charged, plus the pagination cursor behavior.

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 core purpose, then the two modes, then sibling routing, then pricing — a logical sequence with no filler. The sibling-routing sentence is somewhat long relative to its value, but every sentence carries information an agent would otherwise have to guess.

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?

An output schema exists so return values needn't be described, yet the description still sketches what each mode yields (full profile fields vs 50-per-page alphabetical list with cursor). Combined with pricing and sibling routing, nothing needed to invoke it correctly is missing.

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 already 100%, so the baseline is 3, but the description adds real meaning: it clarifies profile accepts a slug or full doximity.com/pub URL, location uses state or state/city slugs, and after carries the next-page cursor from a prior call. This ties parameters to the two modes rather than just restating field types.

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 (US clinician data from Doximity's public directory) and clearly delineates the two retrieval modes: by profile and by location, including exactly what fields each mode returns. An agent can tell this apart from the sibling directories without opening the 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 routes the agent to alternatives explicitly — b2b_manta for small-business keyword search and b2b_bbb for BBB name lookup — and implies the profile-vs-location choice through the two mode descriptions. It stops short of stating when neither mode is appropriate or what happens with no parameters, but the guidance is concrete.

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