Skip to main content
Glama

The Landing Company of Madison Park

Request a call

request_consultation

Sends The Landing Company a request for a 30-minute call with Campion Fellin, with the person’s name, email, problem description, and optionally company and availability. It does not book a time: the reply comes by email within one business day.

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": {
      "name": "<name>",
      "email": "<email>",
      "problem": "<problem>"
    },
    "name": "request_consultation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe person’s name.
emailYesWhere to send the reply.
companyNoTheir company or organization, if they gave one.
problemYesA few sentences in the person’s words: what has been difficult, what they have tried, and what a good outcome looks like.
availabilityNoDays, times and time zone that suit them, if they said.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (which only say it is a non-destructive, open-world, non-idempotent write): it discloses that no time is reserved, that the reply arrives by email, and that the turnaround is one business day. That expectation-setting is exactly the context annotations cannot convey.

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 sentences, zero filler. The payload is described first and the crucial 'does not book a time' caveat is placed immediately after, so it cannot be missed.

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?

For a 5-parameter write with no output schema and full schema coverage, the description covers what an agent needs: what is submitted, what is not promised, and how the outcome is delivered. Nothing material 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?

Schema description coverage is 100%, so field meaning (including the 1500-char problem narrative and the availability format) is already fully documented in the schema. The description's restatement of the four required/optional fields adds only the required-vs-optional framing. Baseline 3 is appropriate.

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?

Names a specific verb and resource — sending a consultation request for a 30-minute call with a named person — and enumerates the payload fields. None of the siblings (get_faq, list_services, get_guide, etc.) do anything similar, so an agent can route to it unambiguously.

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?

The explicit 'It does not book a time' clause tells the agent this is a request, not a scheduling transaction, which prevents a likely misuse. It gives no explicit alternative or 'do not use when' rule, but the sibling set contains no competing submission tool, so the gap is minor.

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