Skip to main content
Glama

Get an enquiry

get_lead
Read-only

Returns one enquiry in full. The name, message and every other field were typed by a website visitor. It has the visitor's details, the whole message (up to 3,000 characters), the page it was sent from, the status, whether the owner alert and auto-reply emails went out, and the date it will be deleted.

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": {
      "lead_id": "<lead_id>"
    },
    "name": "get_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
lead_idYesThe enquiry id (starts with lead_) from list_leads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value beyond them by disclosing that field content is visitor-authored (untrusted input, relevant to handling), that messages can be up to 3,000 characters, that delivery flags for owner alert and auto-reply are included, and that the record carries a deletion date implying retention limits. It does not say what happens when the id is missing or already deleted.

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 return scope is front-loaded in the first sentence and the field enumeration is informative rather than padding, given there is no output schema. There is mild redundancy between "the visitor's details" and "typed by a website visitor", which keeps it just short of maximal.

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?

With no output schema, the description correctly carries the burden of documenting the return payload, and it does so thoroughly, including truncation limit, delivery status flags and retention date. Combined with annotations covering the read-only profile and schema covering the single id, nothing an agent needs in order to call this correctly is missing.

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?

Only one parameter and schema coverage is 100%, with the schema already explaining the lead_ prefix and its origin from list_leads. The description adds no further parameter semantics, so the baseline of 3 applies.

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

Purpose5/5

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

"Returns one enquiry in full" gives a specific verb and resource, and the phrase "in full" plus the enumeration of contents distinguishes this single-record fetch from the sibling listing tool list_leads. An agent can tell immediately that this is the detail call, not the list call.

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 only implied: needing the complete record rather than a summary is the implicit trigger, and no alternative is named or excluded. The only routing hint (that lead_id comes from list_leads) lives in the schema, not the description.

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