Diver Atlas

get_site_plate

Read-only

Full plate for a slug, including verification, sources, and the canonical URL.

Input Schema

Name	Required	Description	Default
`slug`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 27, 2026
- removedInput schema / properties / site
```
Removed value: -{
-  "minLength": 1,
-  "type": "string"
-}
```
- removedInput schema / properties / slug / minLength
```
Removed value: -1
```
- addedInput schema / required
```
Added value: +[
+  "slug"
+]
```
First observedOct 26, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already establish that this is a read-only, non-open-world operation. The description adds useful return-content context (verification, sources, canonical URL), but does not discuss missing-slug behavior, error handling, or response shape.

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?

It is a single efficient sentence with the key scope front-loaded. The jargon "plate" slightly reduces clarity, but there is no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only lookup with no output schema, the description gives a partial sense of what is returned but remains too vague about the structure and slug semantics to be fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions the slug parameter only by name and does not define its format, source, or meaning. With schema description coverage at 0%, this leaves the parameter largely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific operation (retrieving a full plate for a slug) and lists some contents, but "plate" is domain jargon and the description does not clearly distinguish this from siblings like search_sites or list_centres.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies a lookup when you already have a slug, but gives no explicit guidance on when to use this instead of search_sites or list_centres, and no exclusions or prerequisites are stated.

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

All Diver Atlas 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?