Phorme Training

Find a Phorme clinic

find_clinic

Read-only

Use this when the user wants to be seen in person by a physical therapist, sports medicine clinic, chiropractor, sports massage therapist or recovery studio, in a city they name or, when they name none, near the approximate location the assistant shares. It returns up to five Phorme clinic and recovery partners, nearest or best matching first, each with the kind of care, the services it lists, its page on phor.me and a link to ask for an appointment there. It takes a place and a kind of care, never symptoms. It reads only, does not diagnose or treat, shows no prices and books nothing.

Input Schema

Name	Required	Description	Default
`care`	No	The kind of care the user asked for, only if they named one.
`city`	No	The city the user named, for example "Austin".

Output Schema

Name	Required	Description	Default
`limits`	Yes	What this does not cover. Tell the user.
`clinics`	Yes	Clinics, nearest or best matching first: name, care, line, city, country, distance_km, page_url, request_url and services.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

removedInput schema / properties / near_lat

Removed value: -{
-  "description": "Latitude, only if the user shared their position.",
-  "maximum": 90,
-  "minimum": -90,
-  "type": "number"
-}

removedInput schema / properties / near_lon

Removed value: -{
-  "description": "Longitude, only if the user shared their position.",
-  "maximum": 180,
-  "minimum": -180,
-  "type": "number"
-}

AddedOct 17, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that results are capped at five, ordered nearest or best matching first, and include care type, listed services, a phor.me page, and an appointment-request link. It also explicitly states what the tool does not do: diagnose, treat, show prices, or book.

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

Conciseness5/5

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

The description is front-loaded with the primary use case, then adds return behavior and guardrails in a compact sequence. Although it is detailed, every clause contributes useful selection or invocation context.

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?

The definition is complete for a two-parameter, optional-input, read-only search tool: it explains when to use it, how location is resolved, what is returned, and what it must not be used for. An output schema exists, so the description need not fully document the return shape.

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?

With 100% schema description coverage, the schema already documents both parameters, so the baseline is 3. The description adds useful semantic guidance: it takes a place and a kind of care, never symptoms, and clarifies that when no city is named it uses the approximate location shared by the assistant.

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 clearly states the tool finds in-person clinic/recovery partners for a user-named city or approximate location, and distinguishes the resource from symptoms, diagnosis, treatment, and booking. It does not explicitly name a sibling tool alternative, so it is clear but lacks the explicit sibling differentiation that would warrant a 5.

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 a strong when-to-use condition: the user wants to be seen in person by a physical therapist, sports medicine clinic, chiropractor, sports massage therapist, or recovery studio. It also includes boundaries such as 'never symptoms', no diagnosis/treatment, no prices, and no booking, but it does not name the alternative sibling tools to use for those excluded actions.

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

All Phorme Training tools Inspect

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.