Skip to main content
Glama

Promise Land Appraisal public information

Get blank message template

get_blank_message_template
Read-onlyIdempotent

Return a blank SMS or email template with placeholders for the details Alex needs. This tool accepts no personal or property details and does not send, submit, or store a message.

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": {
      "channel": "<channel>"
    },
    "name": "get_blank_message_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesChoose whether the blank message template is formatted for text or email. No message is sent.

Output Schema

NameRequiredDescriptionDefault
templateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety basics are covered. The description adds genuinely new context beyond them: it accepts no personal or property details, and it does not send, submit, or store anything, which tells the agent no side effects or PII exposure should be expected. It does not mention rate limits or the template's static nature, keeping it below a 5.

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 short sentences with no filler; the core purpose leads and the negative scoping follows. Every clause carries information an agent can act on.

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?

An output schema exists, so return values need no explanation, and the single required parameter is fully documented in the schema. Between annotations and the description, an agent can call this correctly; only the relationship of this template to downstream send/compose flows is left implicit.

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?

The single 'channel' parameter has full schema description coverage plus an enum, so the schema does the heavy lifting and baseline is 3. The phrase 'blank SMS or email template' loosely mirrors the enum values without adding format or behavioral detail about how the two variants differ.

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 ('Return') and resource ('blank SMS or email template') plus what the output contains ('placeholders for the details Alex needs'). That is enough to separate it from the listed siblings (business profile, request information, appraisal services), but the description never explicitly contrasts itself with any alternative, so it stops short of a 5.

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: an agent can infer this is the step to take before composing a message, but the description gives no explicit when-to-use, prerequisites, or named alternative for drafting or sending a real message. The closing sentence describes what the tool does not do rather than when to choose it.

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