Skip to main content
Glama

GrowLocal

request_website_preview

Idempotent

Record a local business's request and return the address its owner opens to sign up. Reuse operationId on retries.

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": {
      "request": "<request>"
    },
    "name": "request_website_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNo
placeNo
requestYesWhat the business does and where it is.
operationIdNo
businessNameNo
currentWebsiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context by explaining the idempotency mechanism (reuse operationId) and stating that an address is returned. It does not disclose what side effects recording the request has (e.g., whether the business is contacted or a notification is sent).

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 tight sentences with the primary action front-loaded and the retry rule appended where it belongs. There is no wasted wording, though the brevity comes at the cost of the parameter coverage noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, no output schema, and thin schema descriptions, the definition should explain the argument set and the shape of the returned signup address. Instead it covers one parameter and one behavior, leaving an agent to guess how to populate goal, place, and currentWebsite.

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 only 17%, so the description must compensate and it largely does not. Of six parameters, only operationId gets added meaning (reuse on retries), while goal, place, businessName, and currentWebsite are left entirely to maxLength-only schema entries, and the distinction between 'goal' and 'request' is never clarified.

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?

The description gives a specific verb and resource ('Record a local business's request') plus the outcome ('return the address its owner opens to sign up'), which is enough to distinguish it from the read-only siblings get_website_cost_guide and get_website_offer. It stops short of naming those alternatives or precisely characterizing the return value (URL? signup link?).

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?

'Reuse operationId on retries' is a concrete operational guideline, which is more than most definitions offer. However, there is no explicit when-to-use or when-not-to-use framing, and no pointer to the sibling cost/offer tools that an agent might otherwise consider.

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