Skip to main content
Glama

Get a lab enquiry link

enquiry_link
Read-only

Return a link to the lab's enquiry form on ScopeMatch, prefilled with the test details. The person reviews the form and sends it on the website; this tool sends nothing.

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": {
      "lab": "<lab>"
    },
    "name": "enquiry_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
labYes
samplesNo
materialNo
test_method_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Goes beyond readOnlyHint=true by explicitly stating 'this tool sends nothing' and that the person submits on the website, which is exactly the side-effect disclosure an agent needs. It omits other traits such as link lifetime/expiry or what happens if the lab or test_method_id is invalid.

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 tight sentences, no filler, with the core return value front-loaded and the safety caveat immediately after it.

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?

Adequate on the output side (no output schema, but 'a link' is clear) and on side effects, yet incomplete overall because none of the four undocumented parameters are clarified. For a tool with 0% schema coverage this leaves a real gap an agent could trip over.

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?

Schema description coverage is 0% across four parameters, so the description must carry the load and it does not: it only vaguely gestures at 'test details' being prefilled. Nothing explains what format 'lab' takes, whether 'samples' is a list or free text, what 'material' means, or how 'test_method_id' relates to the prefilled form.

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 and resource: 'Return a link to the lab's enquiry form on ScopeMatch', plus the qualifier that it is prefilled with test details. It is clearly distinct from verify_lab and search_labs in substance, though it never names them.

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?

The second sentence implies the intended workflow (a human reviews and submits the form themselves), which suggests when to reach for this tool, but there is no explicit when-to-use, when-not, or routing to alternatives such as verify_lab or search_labs.

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