Skip to main content
Glama

Dolphin Industrial Parts

Get the site manifest

get_manifest
Read-onlyIdempotent

Site, contact details, endpoints, tools, limits and disclaimer for Dolphin Industrial Parts. Availability and price are quoted per application.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds that the payload includes limits and a disclaimer, which is modest extra context, but it says nothing about response shape, size, or freshness.

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?

Two short sentences with no filler, and the content enumeration is front-loaded. The pricing sentence is tangential to the tool's mechanics but does carry a small routing signal, so it earns partial credit rather than being dead weight.

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 no output schema, the description carries the burden of describing returns, and the enumeration of included fields (site, contacts, endpoints, tools, limits, disclaimer) does that reasonably well for a zero-parameter read. It stops short of stating the format or when to call it, but an agent has enough to invoke it correctly.

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 there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. Schema coverage is reported at 100% with an empty property set, confirming no gap.

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 enumerates the manifest's contents (site, contact details, endpoints, tools, limits, disclaimer) so the resource is identifiable, but it never states a verb ('returns'/'retrieves') and reads as a content list rather than a purpose statement. It does not explicitly contrast itself with siblings like list_catalog or lookup_part, leaving the agent to infer that this is site-level metadata rather than catalog data.

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?

There is no explicit when-to-use guidance or statement of prerequisites. The trailing sentence 'Availability and price are quoted per application' only faintly signals that pricing is not obtained here (implying request_quote), but this is an indirect hint rather than a routing instruction.

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