Yeww

Get a Yeww instructor

get_instructor

Read-onlyIdempotent

Look up one public Yeww instructor by the slug in their profile URL. Returns only information shown on the public profile.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_instructor"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes

Output Schema

Name	Required	Description	Default
`bio`	Yes
`name`	Yes
`slug`	Yes
`rating`	Yes
`sports`	Yes
`resorts`	Yes
`reviews`	Yes
`tagline`	Yes
`verified`	Yes
`languages`	Yes
`avatar_url`	Yes
`price_from`	Yes
`profile_url`	Yes
`specialisms`	Yes
`review_count`	Yes
`years_experience`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine value by disclosing the data scope ('returns only information shown on the public profile'), but says nothing about authentication requirements, rate limits, or behavior when the slug does not resolve.

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?

Two short sentences, zero filler, with the core purpose front-loaded and the data-scope caveat following. Every sentence earns its place.

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 single-parameter read tool with an output schema (so return values need no explanation) and rich annotations, this is nearly complete. The only real omission is error/not-found behavior, which matters somewhat for an openWorldHint lookup.

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?

The single parameter has no schema description (0% coverage), so the description carries the burden and does: it explains that the slug is the identifier appearing in the profile URL, which is real meaning beyond the bare 'string' type. It stops short of specifying format details such as case sensitivity or hyphenation.

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?

States a specific verb ('look up') and a precisely scoped resource ('one public Yeww instructor'), plus the lookup key. An agent can tell this retrieves a single entity, which is clearly different from the sibling search_availability, though the description never names that sibling to make the contrast explicit.

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?

Usage is implied rather than stated: the agent learns the slug comes from the instructor's profile URL, which is a useful precondition. There is no when-not-to-use guidance, no mention of what to do when the slug is unknown or invalid, and no explicit routing to search_availability for discovery-style lookups.

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

All Yeww 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.

Resources

Need Help?