Skip to main content
Glama

Grade a dental employment contract

grade_dental_contract_link
Read-onlyIdempotent

Returns the dentalunlock.com page where a dentist can upload a dental employment contract for an A-F grade, and describes what the free grade and the optional full analysis include. Relevant when a dentist asks whether an associate contract or job offer is fair, about red flags, non-competes, or negotiating. The review itself happens on dentalunlock.com. General information, not legal advice.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a safe, idempotent read; the description goes beyond them by disclosing that the actual review happens off-site on dentalunlock.com and that the tool returns a pointer rather than an analysis. It also explains the free-grade/paid-full-analysis split and adds a 'not legal advice' disclaimer. Minor gaps remain: it does not say whether the returned page is personalized or whether any account or upload is required before use.

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?

The description is front-loaded with what the tool returns, and each later sentence adds useful information: the trigger scenarios, the on-site handoff, and the legal disclaimer. 'The review itself happens on dentalunlock.com' partly repeats the opening sentence about the dentalunlock.com page, which is the only real redundancy.

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 tool takes no parameters, has a rich annotation set, and returns a page reference rather than structured data, so no output schema is needed. The description covers what is returned, what the destination offers, and the limitations an agent must relay to a user.

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 tool takes zero parameters, so the baseline is 4 and there is no parameter meaning the description could add or omit. The schema is fully self-documenting here.

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 uses a specific verb and object: it returns the dentalunlock.com page where a contract can be uploaded for an A-F grade, and it describes what the free grade and the optional full analysis contain. This is clearly distinguishable from siblings such as dental_salary_benchmarks or estimate_dental_malpractice, though it does not explicitly name those siblings as alternatives.

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?

Strong trigger conditions are given: an associate contract or job offer's fairness, red flags, non-competes, or negotiation. What is missing is any explicit exclusion, such as when a job-search tool (search_dental_jobs) would be the better fit for someone weighing an offer, so the agent gets clear context but no stated boundaries.

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