Skip to main content
Glama
Sign In

mcp

by io.seaworthy
OverviewDiscussionsAdmin

get_specialty_guide

Read-only

Retrieve the Seaworthy Insurance coverage guide for a specific profession or medical specialty. Returns structured metadata plus a link to the full guide. Unauthenticated.

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": {
      "profession": "<profession>"
    },
    "name": "get_specialty_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
professionYesProfession slug or free-form profession name (e.g., "crnas", "orthopedic-surgeons", "dentists", "registered nurses").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the read-only/non-destructive safety profile, and the description adds genuinely new context: it is unauthenticated and returns structured metadata plus a link to the full guide. Auth requirements are not something the annotations express, so this materially helps invocation.

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?

Three short sentences, front-loaded with the verb and resource, then return shape, then auth. Every sentence earns its place with no redundancy.

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 one parameter, no output schema, and read-only annotations, the description supplies what is needed: what it returns (metadata plus guide link) and that no auth is required. Only the absence of cross-tool routing guidance keeps it from being fully complete.

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 coverage is 100% and the single profession parameter is well documented with slug and free-form examples. The description only restates the parameter's purpose ('for a specific profession or medical specialty'), adding no syntax or format detail beyond the schema; baseline 3 applies.

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 (Retrieve) and resource (Seaworthy Insurance coverage guide) scoped to a profession or medical specialty. It is clearly distinguishable from the pricing/estimate siblings by being a lookup of guide content, though it never names an alternative explicitly.

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: an agent would infer this is for fetching coverage-guide information for a given profession. There is no statement of when to prefer this over get_education_article or get_verified_facts, nor any exclusion conditions.

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

All mcp toolsInspect
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